Endpoint and key
https://demo.kitwire.dev/mcp
kitwire-public-demo-key-2026
Transport: Streamable HTTP. Auth: send the key as Authorization: Bearer kitwire-public-demo-key-2026.
The demo is public. Everyone uses the same key, so notes you create can be seen by other visitors. They are kept in memory and deleted when the demo restarts. Do not store anything personal.
Claude Code
claude mcp add --transport http kitwire-demo https://demo.kitwire.dev/mcp \
--header "Authorization: Bearer kitwire-public-demo-key-2026"
Then start claude and run /mcp to check that kitwire-demo is connected.
Cursor
Add this to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project):
{
"mcpServers": {
"kitwire-demo": {
"url": "https://demo.kitwire.dev/mcp",
"headers": { "Authorization": "Bearer kitwire-public-demo-key-2026" }
}
}
}
VS Code
For Copilot agent mode, add this to .vscode/mcp.json in a project:
{
"servers": {
"kitwire-demo": {
"type": "http",
"url": "https://demo.kitwire.dev/mcp",
"headers": { "Authorization": "Bearer kitwire-public-demo-key-2026" }
}
}
}
OpenClaw
On a machine running an OpenClaw gateway:
openclaw mcp set kitwire-demo '{"url":"https://demo.kitwire.dev/mcp","transport":"streamable-http","headers":{"Authorization":"Bearer kitwire-public-demo-key-2026"}}'
openclaw mcp probe kitwire-demo
Other clients
Any client that supports remote MCP servers over Streamable HTTP with a custom header works: give it the endpoint and the Authorization header above.
claude.ai and Claude Desktop connectors accept servers with no auth or with OAuth, not a fixed key, so they cannot use this demo. The kit itself supports OAuth for exactly that case.
Things to try
Ask your client in plain language. It picks the right tool:
| Ask | Tool it calls |
|---|---|
| "Convert 42 km to miles" | convert-units |
| "What is the weather in Lisbon for the next 3 days?" | get-weather |
| "Who am I on the kitwire-demo server?" | whoami |
| "Create a note called Test with the text hello" | create-note |
| "List my notes", then "delete the Test note" | list-notes, delete-note |
Everything you see, the tool list, the schemas, the auth check and the structured results, is what you get in the kit, ready for your own tools.
When you are done
claude mcp remove kitwire-demo
In Cursor or VS Code, delete the kitwire-demo entry from the mcp.json file.
Run your own
The same server on your own URL, with your tools, your keys or OAuth, and 27 tests to keep it honest.