Chip MCP MCP server

An official MCP server by Chip that provides AI coding agents with project memory, including session summaries, decisions, and tasks synced from Telegram. It allows agents to maintain context across sessions without accessing the code repository directly, supporting tools for reading memory, searching, and managing project knowledge.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-05Operated by Chip

MCP endpoint (Streamable HTTP)

https://chip-ai.digital/mcp/

Vendor documentation

What you can do with it

Sync project decisions and session summaries to AI agents
Retrieve tasks and notes from Telegram within the IDE
Maintain project context across multiple coding sessions
Provide read-only access to project memory for agents

Tools advertised by the last live check:

whoami
list_projects
read_journal
read_project_dialog
get_project_map
read_map_section
get_project_context
search_project
list_files
read_project_file
create_project
rename_project
archive_project
save_session_summary
add_note
whats_new
list_tasks
complete_task
add_task
notify_me
set_reminder
ask_user
check_confirmation
upload_project_file
finalize_upload
attach_file
generate_image

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http chip-mcp https://chip-ai.digital/mcp/

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add chip-mcp --url https://chip-ai.digital/mcp/

Cursor

Merge this server into .cursor/mcp.json in your project, then enable chip-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "chip-mcp": {
      "url": "https://chip-ai.digital/mcp/"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "chip-mcp": {
      "type": "streamableHttp",
      "url": "https://chip-ai.digital/mcp/",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start chip-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "chip-mcp": {
      "type": "http",
      "url": "https://chip-ai.digital/mcp/"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http chip-mcp https://chip-ai.digital/mcp/

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "chip-mcp": {
      "url": "https://chip-ai.digital/mcp/"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "chip-mcp": {
      "serverUrl": "https://chip-ai.digital/mcp/"
    }
  }
}

See all 957

Do you run Chip MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing