Chip MCP

Name: Chip MCP
Author: zapret-digital

by zapret-digitalversion 1.3.1i★ –iRuns in the cloud

Registry namedigital.chip-ai/chip

Install

Overview

Description from the maker (original English)

Project memory, tasks and Telegram notifications for your coding agent. Chip account required.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs in the cloud
Transport: Streamable HTTP
Category: Chat & email

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on the maker’s server: what you ask it goes through their server.
The registry lists no key to fill in.

You need

Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

Open Settings → Connectors
Press Add custom connector
Paste the address below and press Add
If it asks you to sign in, sign in with the maker

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

Run this in your terminal

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

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

Open ChatGPT on the web → Settings → Connectors (Apps)
Press Create or Add (some plans need Developer mode under Advanced first)
Paste the address below, give it a name and save
If it asks you to sign in, sign in with the maker

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

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified against the domain chip-ai.digital (the registry checks domain ownership)
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
… Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
… Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Compared with others in Chat & emaili

More stars than 0% of the other 1772 servers in this category
Published to the registry more recently than 35% of the other 1772 servers in this category
Basic checks equal to or better than 100% of the other 1772 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Chip MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.3.1) reached the registry 2 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Vexa, emailmd, MCP WhatsApp Cloud

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Vexa

by Vexa-ai

Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.

Runs in the cloud★ 2,949Apache-2.0Updated 2 months ago

Install

emailmd

by anypost

Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.

Computer or cloud★ 1,385MITUpdated 31 days ago

Install

MCP WhatsApp Cloud

by codespar

MCP server for WhatsApp Cloud API (Meta) — messages, media, and templates via Graph API

Runs on your computer★ 277MITUpdated 5 months ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Chip MCP

Project memory, tasks and Telegram notifications for your coding agent.

Русская версия · chip-ai.digital/mcp

Chip is an assistant living in Telegram. This MCP server connects your IDE agent — Claude Code, Cursor, anything that speaks MCP — to the same account. Decisions you made yesterday, notes your agent wrote last session, tasks you assigned from your phone: all still there when the next session starts with an empty context window.

Language note. Chip is a Russian-language product: the tools answer in Russian

and billing is in rubles. Everything works from any country, but if you don't read

Russian, the responses will not be useful to you.

Why bother

Returning to a project costs 63 tokens instead of 2538. Your agent calls whats_new and gets only what changed since its last visit, not the whole project again. Measured 2026-09-10 on a reference mature project with real tiktoken o200k_base counting — not an estimate:

scenario	before	after
first visit to a project	2538 tokens	2284 tokens
returning, nothing changed	2538 tokens	63 tokens
returning after a day of edits	2538 tokens	295 tokens

A read-only token costs less to even list. The tool list is paid for by every session before the first call: 27 tools = 2905 tokens, the 11 read-only ones = 1155. If your agent only reads the project, issue a read token and save 1750 tokens per session.

Your agent can reach you. notify_me pushes a message to your Telegram when a long build finishes; ask_user asks a question with buttons and check_confirmation picks up the answer later — so an agent working alone can wait for a human decision instead of guessing.

Install

You need a free account: open @ChipAI_robot in Telegram → mini app → Chip MCP → issue a token (chip_mcp_…). Choose read if you want the agent to look but never touch.

Claude Code

claude mcp add --transport http chip https://chip-ai.digital/mcp --header "Authorization: Bearer chip_mcp_YOUR_TOKEN"

Cursor — ~/.cursor/mcp.json (or .cursor/mcp.json in the project):

"mcpServers": { "chip": { "url": "https://chip-ai.digital/mcp", "headers": { "Authorization": "Bearer chip_mcp_YOUR_TOKEN" } } } }

Any other client that takes an mcpServers entry with url + headers works the same way. See docs/clients.md for more.

Then tell your agent to start with whats_new — the server's own instructions say so too, so most agents do it unprompted.

Claude Code plugin

Claude Code can install everything at once — the server, the session ritual and two commands — instead of you wiring up the config by hand.

export CHIP_MCP_TOKEN=chip_mcp_YOUR_TOKEN

claude plugin marketplace add zapret-digital/chip-mcp claude plugin install chip@chip-ai

The token lives only in CHIP_MCP_TOKEN. It is never written into the plugin files, and never into .chip.json.

What the plugin adds:

the chip MCP server, pointed at https://chip-ai.digital/mcp/ — the address is a literal in the plugin, not something the environment can re-point;
/chip:start and /chip:finish — the same session ritual as the server's start and finish prompts, for clients that don't render prompts;
three hooks: on session start the project delta goes into the context; before context compaction and on stop the agent is reminded to save the summary.

The hooks need a .chip.json in the repository root to know which project this is:

{ "project_id": 12 }

The mini app sends it to you — project settings, «Правила для IDE-агента», next to AGENTS.md. Telegram strips the leading dot from attachment names, so rename the file back to .chip.json after saving. Without the file the hooks stay quiet — except for one line at session start saying this repository has no .chip.json. The plugin still works, the session just starts without the delta.

The hooks never block a session — no token, no network, no python3 or curl, and you get one line of explanation instead of a failed start.

*For local development:* CHIP_MCP_URL re-points the hooks only, and only at the production address or a loopback stand (http://127.0.0.1:PORT/mcp/); anything else is refused. The MCP channel itself ignores the variable, so no repository can send your token to its own host through .claude/settings.json.

Tools

27 tools. read tokens get the 11 marked *read*; full tokens get everything.

Tool	Access	Arguments
`add_note`	write	`project_id`, `text`, `kind`
`add_task`	write	`project_id`, `text`
`archive_project`	write	`project_id`
`ask_user`	write	`question`, `options`
`attach_file`	write	`filename`, `size_bytes`
`check_confirmation`	write	`ask_id`
`complete_task`	write	`task_id`, `result`
`create_project`	write	`name`
`finalize_upload`	write	`upload_id`
`generate_image`	write	`prompt`, `project_id`
`get_project_context`	read	`project_id`, `depth`
`get_project_map`	write	`project_id`
`list_files`	read	`project_id`
`list_projects`	read	—
`list_tasks`	read	`project_id`
`notify_me`	write	`text`, `upload_id`
`read_journal`	read	`project_id`, `offset`
`read_map_section`	read	`project_id`, `section`
`read_project_dialog`	read	`project_id`, `session_id`
`read_project_file`	read	`project_id`, `filename`, `page`
`rename_project`	write	`project_id`, `name`
`save_session_summary`	write	`project_id`, `text`
`search_project`	read	`query`, `project_id`, `kind`, `since`
`set_reminder`	write	`text`, `when`
`upload_project_file`	write	`project_id`, `filename`, `size_bytes`, `content`
`whats_new`	read	`project_id`, `since`, `session`
`whoami`	read	—

get_project_map reads a table of contents but is listed as *write*, and that is deliberate: fetching it also refreshes the project map, so a read-only token does not get it. read_map_section reads a single entry without side effects.

Machine-readable: spec.json, generated from the server's own tool registry — see below.

What the server can and cannot see

It has no access to your filesystem. It only ever receives what your agent explicitly passes as arguments. Nothing scans your repository.
Call arguments and results are not logged. The usage log stores the tool name, duration and success flag — nothing else.
A `read` token cannot write. Enforced on the call itself, not just by hiding tools from the list.
Tokens are stored as SHA-256. The raw value is shown once, at issue time.
Listing tools needs no token, so directories can index this server. Every actual call does.

Verify the spec yourself

spec.json in this repo is generated from the live server's tool registry, so it cannot quietly drift from reality. Check it against production yourself:

./scripts/verify.sh

It diffs the committed spec against https://chip-ai.digital/mcp/spec.json.

Pricing

Connecting is free. Reading your own projects is free. Writes, Telegram messages and image generation are metered against your Chip plan — the tools tell your agent when a limit is reached and what to do about it. Plans live in the Telegram bot.

License

MIT for the contents of this repository (spec, docs, scripts). The Chip service itself is proprietary.

Chip MCP

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Chat & emaili

Common questions

Alternatives

Vexa

emailmd

MCP WhatsApp Cloud

README from the maker

Chip MCP

Why bother

Install

Claude Code plugin

Tools

What the server can and cannot see

Verify the spec yourself

Pricing

Links

License