Chipp Memory and schedules MCP Server

by chipp Your server? Claim it

answering

Chipp Memory and schedules is answering right now. Last checked 8 min ago.

Chipp: a project's memory, circles, and scheduled tasks

Uptime history 6 days of history

6 days agonow

100.0%

Uptime 24h

91 of 91 checks

—

Tools

hidden behind auth

288 ms

Response time

average over 24h

OAuth sign-in

Access

streamable-http

Nothing serious here today

Today is the operative word: we check Chipp Memory and schedules every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add chipp-memory --transport http https://mcp.chipp.ai/mcp/memory

Settings → Connectors → Add custom connector, then paste this address

https://mcp.chipp.ai/mcp/memory

~/.codex/config.toml

[mcp_servers.chipp-memory]
url = "https://mcp.chipp.ai/mcp/memory"

.cursor/mcp.json

{
  "mcpServers": {
    "chipp-memory": {
      "url": "https://mcp.chipp.ai/mcp/memory"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "chipp-memory": {
      "type": "http",
      "url": "https://mcp.chipp.ai/mcp/memory"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.chipp.ai/mcp/memory	streamable-http	sign-in	477 ms	8 min ago

Alternatives to Chipp Memory and schedules

same job, measured the same way

Motion MCP by usefulapi

by usefulapi

Read tasks, projects, workspaces and schedules; create tasks in Motion.

7 tools answering

Madda Tasks

by maddatech

Project scheduling: Gantt chart, dependencies, baselines, reports and AI agents

answering

Chip MCP

by chip-ai

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

32 tools answering

Mindpm

by umitkavala

Project memory and a control plane for AI coding agents.

133 installs/wk local only

Clickup

by mcparmory

Manage tasks, lists, checklists, comments, and project workflows

222 installs/wk local only

Stele

by stele-ai

Shared project memory for AI coding agents: decisions, lessons, risks and tasks in one graph.

answering

RepoMemory

by repomemory

Shared project memory for coding agents: decisions, lessons, guardrails and tasks per repository.

5 tools answering

Basecamp

by basecamp

Basecamp's official server: projects, to-dos, cards, messages, docs, schedules, and Campfire.

answering

Chipp Memory and schedules — questions

Answers built from our own checks of this server.

Why is there no tool list for Chipp Memory and schedules?

The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.

Is Chipp Memory and schedules working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 288 ms. The bar chart above shows every period we have measured.

How do I connect Chipp Memory and schedules?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.

How do you sign in to Chipp Memory and schedules?

No API key is involved. Chipp Memory and schedules answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.

How fast is Chipp Memory and schedules?

It answers our handshake in 288 ms on average, which is faster than 50% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.