Pochi LogoPochi Docs

MCP (Model Context Protocol)

The Model Context Protocol (MCP) revolutionizes how Pochi interacts with external services, databases, and APIs. Think of MCP as a universal adapter that connects Pochi to virtually any data source or tool, dramatically expanding what your AI assistant can accomplish.

Configure

Use the VSCode command Pochi: Open MCP Server Settings to open the settings.

{
  "mcp": {
    "context7": {
      "command": "npx",
      "args": ["@upstash/context7-mcp"]
    }
  }
}

After saving the configuration, you will see the MCP server appear in the Tools section of Pochi's settings page.

MCP Server Context7

You can use the toggle switch to enable or disable the MCP server entirely. You can also click on the tool badge to toggle individual tools within the MCP server.

Examples

Local MCP Servers (Stdio Transport)

{
  "filesystem": {
    "command": "npx",
    "args": [
      "-y",
      "@modelcontextprotocol/server-filesystem",
      "/path/to/allowed/files"
    ],
    "env": {
      "HOME": "/Users/yourname"
    }
  }
}

Remote MCP Servers (HTTP Transport)

Custom API Server

{
  "my-api": {
    "url": "https://api.mycompany.com/mcp",
    "headers": {
      "Authorization": "Bearer your-api-token",
      "X-API-Version": "v1"
    }
  }
}

SSE (Server-Sent Events) Server

{
  "realtime-data": {
    "url": "https://data.example.com/mcp/sse",
    "headers": {
      "Authorization": "Bearer your-token"
    }
  }
}

Configuration Hierarchy

Pochi supports hierarchical MCP configuration with both global (user-level) and workspace-specific settings.

  1. Global Configuration: ~/.pochi/config.jsonc - Your default MCP servers available across all projects
  2. Workspace Configuration: .pochi/config.jsonc - Project-specific MCP servers that override or extend global settings

The workspace configuration takes precedence and is merged with the global configuration, allowing you to:

  • Add project-specific MCP servers
  • Override global server configurations for specific projects
  • Maintain different MCP setups for different codebases

Global MCP Configuration Example (~/.pochi/config.jsonc)

{
  "mcp": {
    "context7": {
      "command": "npx",
      "args": ["@upstash/context7-mcp"]
    },
    "filesystem": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-filesystem",
        "/Users/yourname/Documents"
      ]
    }
  }
}

Workspace MCP Configuration Example (.pochi/config.jsonc)

{
  "mcp": {
    "project-db": {
      "command": "npx",
      "args": ["@modelcontextprotocol/server-sqlite", "./database.db"]
    },
    "filesystem": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-filesystem",
        "./src"
      ]
    }
  }
}

In this example:

  • The context7 server from global config will be available
  • The workspace-specific project-db server will be added
  • The filesystem server configuration will be overridden to only access the project's src directory