emnify MCP server

The emnify MCP server is a hosted endpoint at https://emnify.mcp.kapa.ai that lets AI tools query emnify documentation directly from your development environment. It’s hosted by Kapa and exposes a search_emnify_knowledge_sources tool that performs semantic search over emnify’s published documentation.

For background on how emnify uses Kapa and what data the server can access, see AI assistance at emnify.

About MCP

The Model Context Protocol (MCP) is an open standard that lets AI tools connect to external data and tool sources through a shared protocol. An MCP server exposes a set of tools or resources, and an MCP client (such as Cursor or Claude Code) discovers and calls them on your behalf during a conversation.

The emnify MCP server exposes a single tool that searches emnify documentation, so questions you ask in a supported client can be answered with content pulled directly from emnify docs.

Before you begin

You need:

  • An MCP-compatible client. This guide covers Cursor, Claude Code, Claude Desktop, VS Code, ChatGPT, and Codex.
  • A Google or GitHub account, used to sign in on first connection.

The emnify MCP server is public and authenticates via Google or GitHub on first connection. You don’t need an API key or application token in your client configuration.

Configure your client

Pick your client and follow the instructions in the corresponding tab.

1

Open ~/.cursor/mcp.json in your editor. Create the file if it doesn’t exist.

2

Add an emnify entry to the mcpServers object:

1{
2  "mcpServers": {
3    "emnify": {
4      "type": "http",
5      "url": "https://emnify.mcp.kapa.ai"
6    }
7  }
8}

If the file already contains other MCP servers, add emnify alongside them inside the existing mcpServers object.

3

Save the file, then fully quit and reopen Cursor for the new server to load.

Sign in

On the first request that uses the emnify MCP server, your client opens a browser window to authenticate with Google or GitHub. After you sign in, the client stores the token and reuses it for future requests. You may be asked to re-authenticate periodically.

Verify the connection

To confirm the server is working, ask your client a question about emnify that requires looking up documentation, for example:

Explain how to create an application token in emnify.

The client should invoke the search_emnify_knowledge_sources tool and return an answer based on emnify documentation.

Troubleshooting

Most clients only read MCP configuration at startup. Fully quit and reopen the application. Closing the window isn’t always enough on macOS.

Make sure a default browser is set on your system. If the window opens but the redirect back to the client fails, try signing in with a different provider (Google or GitHub).

The emnify MCP server allows 40 requests per user per hour and 200 per user per day. Wait until the limit resets, or batch related questions into a single request.