Chipp Memory and schedules MCP server
ai.chipp · Updated
Chipp: a project's memory, circles, and scheduled tasks
At a glance
Chipp Memory and schedules is an MCP server in the AI & Memory category. It is hosted remotely and connects over HTTP, and declares no required credentials. It scores D (23/100) on the MCP Skills Hub health score as of Oct 28, 2026.
One-click install
Opens your editor and pre-fills the config. Your editor will ask before adding it.
How to install Chipp Memory and schedules in your AI client
Setup for Claude Code, Claude Desktop, Cursor, Codex, Windsurf, Cline and VS Code — copy-paste ready.
How to install Chipp Memory and schedules in Claude CodeAnthropic's agentic CLI
Add the server
bashclaude mcp add --transport http chipp-memory https://mcp.chipp.ai/mcp/memoryVerify it's connected
bashclaude mcp listSharing it with your team?
Add `--scope project` to write it to .mcp.json in the repository root, which you can commit (with the secrets left as environment variables).
Use it in a session
Ask Claude to use the tools this server exposes. It discovers them automatically.
How to install Chipp Memory and schedules in Claude DesktopDesktop app (MCP config)
Open your MCP config
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json
Add this server
json{ "mcpServers": { "chipp-memory": { "command": "npx", "args": [ "-y", "mcp-remote", "https://mcp.chipp.ai/mcp/memory" ] } } }Why the wrapper?
This is a remote (HTTP) server and Claude Desktop only launches local processes, so mcp-remote proxies the connection. It will open a browser window if the server needs OAuth.
Restart Claude Desktop
The tools appear under the 🔌 menu once the app reloads.
How to install Chipp Memory and schedules in CursorAI-first code editor
Create / edit .cursor/mcp.json in your project
json{ "mcpServers": { "chipp-memory": { "url": "https://mcp.chipp.ai/mcp/memory" } } }Enable it
Cursor Settings → MCP → toggle the server on. Tools become available to the Composer/Agent.
How to install Chipp Memory and schedules in Codex CLIOpenAI coding agent
Add to ~/.codex/config.toml
toml[mcp_servers.chipp-memory] command = "npx" args = ["-y", "mcp-remote", "https://mcp.chipp.ai/mcp/memory"]Why the wrapper?
Codex runs MCP servers as local processes, so mcp-remote bridges this HTTP endpoint to stdio.
Run Codex
Codex loads MCP servers from config.toml on startup and exposes their tools to the agent.
How to install Chipp Memory and schedules in WindsurfCodeium's agentic IDE
Edit ~/.codeium/windsurf/mcp_config.json
json{ "mcpServers": { "chipp-memory": { "serverUrl": "https://mcp.chipp.ai/mcp/memory" } } }Reload
Windsurf → Cascade → refresh MCP servers. Cascade can now call the tools.
How to install Chipp Memory and schedules in ClineVS Code autonomous agent
Open Cline → MCP Servers → Configure
Adds to cline_mcp_settings.json.
Add the server
json{ "mcpServers": { "chipp-memory": { "type": "streamableHttp", "url": "https://mcp.chipp.ai/mcp/memory" } } }
How to install Chipp Memory and schedules in VS CodeCopilot / MCP support
Create .vscode/mcp.json
json{ "servers": { "chipp-memory": { "type": "http", "url": "https://mcp.chipp.ai/mcp/memory" } } }Start it
VS Code shows a ▶ Start action above the server entry. Agent mode (Copilot Chat) can then use the tools.
What tools does Chipp Memory and schedules expose?
This server requires credentials before it will list its tools, so we cannot enumerate them here. Connect it in your client to see what it offers.
What the code can do
This is a remote server — nothing is installed or run on your machine, so there is no local code to analyze. What it can reach is described above: your requests go to the provider's host.
Before you install
Signals gathered from the source repo and package registry — not a safety verdict.
What it can reach
- Third-party hosted service — Your requests and any data in them are sent to mcp.chipp.ai.
- No local execution — Nothing is installed or run on your machine.
- No source repository — This registry entry does not link to a public repo, so its code cannot be reviewed before you install it.
Client compatibility
Health score
D · 23Maintenance, adoption, transparency and packaging — not a safety audit. How this is calculated
- Maintenance30%not measurable
No commit history available.
- Adoption20%not measurable
No usage data available.
- Transparency20%0%
0/4: ✗ public source repo, ✗ declared license, ✗ documentation, ✗ discoverable tool list.
- Provenance15%0%
No source repository to trace the code back to.
- Packaging15%75%
Remote endpoint; authentication requirements not declared.
Alternatives to Chipp Memory and schedules
- SPM - Structured Project MemoryB · 69Durable, shareable and governed project memory with smart triage and explicit project composition.
- Cairn.ink MemoryA · 80Cross-session memory for AI agents with a Source Receipt for every memory, over MCP.
- Atlaso MemoryB · 68Atlaso, the AI memory layer: one shared, persistent memory for every AI tool you connect.
- ctxstore — memory that follows you across modelsB · 65Persistent memory for AI agents: keyed facts, a wake bundle each session, one memory in every model.
Maintain Chipp Memory and schedules? Add a badge to your README
Shows its health grade, and links readers to install steps for every client.
[](https://mcp-skills-hub.vercel.app/mcps/ai-chipp-chipp-memory)Catalog data refreshed . Something wrong? Report it.