Skip to main content
DarkFunnels speaks standard MCP, so it works in any client that supports it. It is always the same URL:
Nothing to register, no access to request: on connecting, the client discovers on its own how to authorize you and opens your browser. Sign in with the same account you use for the dashboard.

​
Cursor

Edit ~/.cursor/mcp.json (global) or .cursor/mcp.json (that project only):
Cursor opens the browser the first time only, then stores the session.

​
VS Code

Edit .vscode/mcp.json in your project, or the one in your user profile:
VS Code is where people get it wrong most, over two details:
  • The root key above is servers, not mcpServers as in Cursor. With the wrong key VS Code ignores the entire file and says nothing.
  • "type": "http" is required. Without it the remote connection never comes up.

​
Gemini CLI

Edit ~/.gemini/settings.json, or the project’s .gemini/settings.json. Watch the field name: here the URL goes in httpUrl, not url:
Gemini CLI discovers the authorization on its own and stores the token in ~/.gemini/mcp-oauth-tokens.json, refreshing it when it expires.

​
Any other client

Windsurf, Zed, Claude Desktop and the rest follow the same pattern. The only things that change between them are three details, and they are worth checking in your client’s own docs before fighting the file:
  1. What the root key is called — mcpServers in almost all of them, servers in VS Code.
  2. What the URL field is called — url in almost all of them, httpUrl in Gemini CLI.
  3. Whether a type has to be declared — "type": "http" in VS Code.

​
If your client runs out of room for tools

Some clients cap how many tools the model can hold at once — Windsurf around 100, VS Code 128 — counting all your servers together. DarkFunnels ships 45 with ?features=all, so if you already have several connectors you may fall short. The fix is to ask only for what you are going to use. The list replaces the base set rather than extending it:
The groups are in the tool reference. And if you want to look without being able to touch anything:

​
Headless (no human present)

Not today. Connecting requires a person to authorize in a browser with their account, so an agent running on its own — a cron job, a worker, OpenAI’s Agents SDK or Claude’s Agent SDK — cannot connect by itself. We are working on agent keys for that. In the meantime, if you need to automate something with no human present, write to us and we’ll look at it case by case.
If your client can’t see your business, or sees it empty, it is almost always the same thing: you authorized with a different account and are connected to another workspace. Ask your assistant “which account are you connected to?” and, if it isn’t the right one, remove the connector and connect it again.
Last modified on September 4, 2026