← All integrations

DNSFilter MCP server

259 operations0 webhooks

Cloud DNS security and content filtering - manage networks, policies, roaming clients, block pages, and traffic reporting.

Use DNSFilter in Claude, ChatGPT, Cursor or another MCP client

Connect DNSFilter once in Corsair, then add one MCP address to your agent.

Connect DNSFilter
Setup steps for Claude, ChatGPT, Cursor and Claude Code

Building your own app on the Corsair SDK? Get API keys

Try DNSFilter with your agent

Connect DNSFilter, then paste this into Claude, ChatGPT or Cursor. For ideas from other apps, see the use cases.

Using Corsair, show me what you can do in DNSFilter on my account, then run one read-only example and show me the result.

Runs once, when you ask

DNSFilter tools and triggers

Tools are what your agent can do in DNSFilter through Corsair's MCP server. Triggers are the DNSFilter events a routine can start from.

Traffic Reports

  • QpsRead-only

    QPS for traffic reports

    trafficReports.qps

  • Qps Active AgentsRead-only

    QPS active agents for traffic reports

    trafficReports.qpsActiveAgents

  • Qps Active OrganizationsRead-only

    QPS active organizations for traffic reports

    trafficReports.qpsActiveOrganizations

  • Query LogsRead-only

    Query logs for traffic reports

    trafficReports.queryLogs

  • Top AgentsRead-only

    Top agents for traffic reports

    trafficReports.topAgents

  • Top Application CategoriesRead-only

    Top application categories for traffic reports

    trafficReports.topApplicationCategories

  • Top CategoriesRead-only

    Top categories for traffic reports

    trafficReports.topCategories

  • Top CollectionsRead-only

    Top collections for traffic reports

    trafficReports.topCollections

  • Top DomainsRead-only

    Top domains for traffic reports

    trafficReports.topDomains

  • Top NetworksRead-only

    Top networks for traffic reports

    trafficReports.topNetworks

  • Top Organizations RequestsRead-only

    Top organizations requests for traffic reports

    trafficReports.topOrganizationsRequests

  • Top UsersRead-only

    Top users for traffic reports

    trafficReports.topUsers

Connect DNSFilter to Claude, ChatGPT or Cursor

  1. 1

    Connect DNSFilter in Corsair

    Add your DNSFilter API key once in Corsair. Corsair stores the credential encrypted and makes the DNSFilter API calls for your agent, so it never goes into a prompt or a config file. Connect DNSFilter

    If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs DNSFilter. On a ChatGPT personal plan, connect DNSFilter here first.

  2. 2

    Add Corsair's MCP server to your agent

    Every client uses the same address:

    https://mcp.corsair.dev/mcp
    Open Customize → Connectors → Add custom connector, paste the address, then select Connect.

    Codex, Gemini CLI, VS Code, Zed and other clients with OAuth sign-in work the same way. Clients without it, such as GitHub Copilot's coding agent, use a link's own address and an API key. Setup for every client

  3. 3

    Sign in and choose what needs your approval

    Your client opens Corsair to sign in. Pick a link: the apps your agent can use and a mode that decides what it may do without asking. In the default Cautious mode, DNSFilter's read and write operations run right away and its 27 destructive operations wait for your approval. Strict mode asks before every write and refuses destructive operations, and Read mode allows reads only.

FAQ

Install corsair and @corsair-dev/dnsfilter, add the DNSFilter plugin, and connect with an API key. Then call methods like corsair.dnsfilter.api.agentLocalUserBulkDeletes.counts() from your app. Corsair syncs data per tenant.

Yes. DNSFilter requires an API key from your DNSFilter account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit DNSFilter, GitHub, Notion, Stripe, and the rest. Trigger DNSFilter from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for cloud dns security and content filtering - manage networks, policies, roaming clients, block pages, and traffic reporting. Common builds include sync jobs, admin tooling, and agents that call DNSFilter APIs from your backend. Local DB entities let you query synced DNSFilter records without hitting the API on every read.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per DNSFilter API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/dnsfilter in the open repo. When DNSFilter ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your DNSFilter data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store DNSFilter data on your behalf.

Yes. Add https://mcp.corsair.dev/mcp as a custom connector or MCP server in Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex or any client that supports remote MCP servers with OAuth sign-in, then sign in to Corsair. On ChatGPT personal plans, custom servers currently get read tools only.

Yes. Put DNSFilter on a link in Strict mode and every write waits for your approval, while destructive actions are refused. The default Cautious mode asks only before the 27 destructive DNSFilter operations. You can change a link's mode at hub.corsair.dev/me.