mcpbeat Sign in

Kilt MCP Server

answering

Kilt is answering right now. Last checked 5 min ago.

Collects the open points of your AI conversations on a color board, so no idea or decision is lost.

Uptime history 16 days of history
16 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
621 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

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

Three servers free · no card

Connect this server

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

run in your terminal
claude mcp add kilt --transport http https://app.kiltwork.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://app.kiltwork.com/mcp
~/.codex/config.toml
[mcp_servers.kilt]
url = "https://app.kiltwork.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "kilt": {
      "url": "https://app.kiltwork.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "kilt": {
      "type": "http",
      "url": "https://app.kiltwork.com/mcp"
    }
  }
}

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

URLTransportStateLatencyChecked
https://app.kiltwork.com/mcp streamable-http sign-in 645 ms 5 min ago

Alternatives to Kilt

same job, measured the same way
The Agent Commons
by affix-io

Open public message board where AI agents read and post conversations. Remote MCP.

23 tools answering
Memnest
by blue-b

Local memory for coding AIs: search past conversations and decisions from the original text.

local only
Living Brain
by livingbrain

Turn your notes, links and conversations into a Living Brain your AI tools share and build on.

answering
K8s Removed API Lint
by jmshinhwa

15 checks for the apiVersions kubectl no longer serves, on the manifest open in your editor

162 installs/wk local only
Configure Memory
by configure-dev

Bring your saved preferences, project decisions, and useful context into your next AI conversation.

9 tools answering
Engramic
by engramic

Your organisation's decisions, goals and constraints, with the reasoning, for every agent.

answering
Benchwarmers
by wendellresearch-ai

Ask a collection of LLMs at once through your Benchwarmers server; verdicts pick the next panel.

2 874 installs/wk local only
SimplyBoost
by simplyboost

Ask your SimplyBoost AI agents, work conversations and leads, and manage their knowledge.

answering

Kilt — questions

Answers built from our own checks of this server.

Why is there no tool list for Kilt?
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 Kilt 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 621 ms. The bar chart above shows every period we have measured.
How do I connect Kilt?
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 Kilt?
No API key is involved. Kilt 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 Kilt?
It answers our handshake in 621 ms on average, which is faster than 16% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.