MCP servers

Connect Model Context Protocol servers to Assumer, local or remote with OAuth, and control which of their tools the agent is allowed to use.

The Model Context Protocol (MCP) lets you plug extra tools into Assumer, for example browser automation, your issue tracker, a database or internal APIs.

Add a server

The quickest way is the interactive command:

assumer mcp add
assumer mcp list

Inside the terminal UI, open /mcps to see connected servers and their tools.

Configure servers in your project

{
  "mcp": {
    "playwright": {
      "type": "local",
      "command": ["npx", "-y", "@playwright/mcp@latest"]
    },
    "github": {
      "type": "remote",
      "url": "https://api.githubcopilot.com/mcp/"
    }
  }
}

• Local servers run as a command on your machine (stdio).
• Remote servers connect over HTTP. If a server needs sign-in, run assumer mcp auth <name>. Use assumer mcp logout <name> to remove stored credentials, and assumer mcp debug <name> when a connection fails.

Permissions

MCP tools follow the same allow, ask and deny rules as built-in tools. See Permissions.

Looking for servers worth installing? Read MCP servers for coding agents.