Connect an Agent

Mite serves a Model Context Protocol server. Connect a coding agent to it, and the agent can work through your inbox, move the roadmap, and ship release notes.

https://usemite.com/mcp

The MCP server is included on paid plans.

Choose how the agent signs in

There are two ways to connect. Each client below shows both.

	Sign in	Agent key
How	The client opens a browser and you sign in to Mite. No key is copied.	You send a secret key as a bearer token.
Reaches	Every app you own	One app
Use it for	Your own editor or chat app	CI, scheduled jobs, and anything that can't open a browser

To get an agent key, open Settings → Agents in the Mite dashboard, click Create key, and copy it. Mite shows the key once. Keep it in the MITE_AGENT_KEY environment variable, not in your repository.

The dashboard shows these same instructions under Settings → Agents, with copy buttons.

Claude

Claude Code

claude mcp add --transport http mite https://usemite.com/mcp

With Sign in, run /mcp in Claude Code, select mite, and sign in to Mite.

To share the server with everyone on a project, commit a .mcp.json at the project root. Each person sets MITE_AGENT_KEY in their own environment.

.mcp.json

{
  "mcpServers": {
    "mite": {
      "type": "http",
      "url": "https://usemite.com/mcp",
      "headers": { "Authorization": "Bearer ${MITE_AGENT_KEY}" }
    }
  }
}

Claude on the web and desktop

Open Customize → Connectors.
Click Add, then Add custom connector.
Name it Mite and paste https://usemite.com/mcp as the server URL.
Click Add, then sign in to Mite.

On a Team or Enterprise plan, an owner adds the connector under Organization settings → Connectors. Members then click Connect on it.

Codex

codex mcp add mite --url https://usemite.com/mcp

With Sign in, Codex opens a browser to sign in to Mite. Run codex mcp login mite to sign in again later.

You can also add the server to ~/.codex/config.toml by hand:

~/.codex/config.toml

[mcp_servers.mite]
url = "https://usemite.com/mcp"

Cursor

Add Mite to Cursor installs the server in one click. Sign in to Mite when Cursor asks.

Or add it to .cursor/mcp.json in your project, or ~/.cursor/mcp.json for every project:

.cursor/mcp.json

{
  "mcpServers": {
    "mite": {
      "url": "https://usemite.com/mcp"
    }
  }
}

Any other client

Any client that speaks MCP over streamable HTTP can connect.

Sign in. Add https://usemite.com/mcp as a remote server. A request without a token gets 401 with a WWW-Authenticate header that points the client to Mite's OAuth metadata, so clients that support OAuth sign in on their own.
Agent key. Send Authorization: Bearer mite_agent_... on every request.

Most clients read a config shaped like this one:

{
  "mcpServers": {
    "mite": {
      "type": "http",
      "url": "https://usemite.com/mcp",
      "headers": { "Authorization": "Bearer ${MITE_AGENT_KEY}" }
    }
  }
}

Leave out headers to sign in instead. The environment variable syntax differs by client: Claude Code uses ${NAME} and Cursor uses ${env:NAME}.

What the agent can do

A key with Read only access can list and read bug reports, feature requests, crash groups, and releases. Read and write access can also triage and comment on reports, move the roadmap, publish releases, and draft announcements. A sign-in connection has read and write access to every app you own.

The full tool list, errors, and rate limits are in the developer docs.

On this page