We have upgraded the Cartographer MCP server to the latest version of the Model Context Protocol spec. Your spaces, projects and cards are unchanged, and every tool does what it did before. What changed is how the server describes its tools and how it returns results.
Most AI tools load the list of tools once, when they first connect, and keep using that copy. If yours is still holding the old list, Cartographer calls may fail or come back empty until it reloads.
Reconnecting Cartographer
Refresh or reconnect Cartographer in your AI tool so it loads the new tools. You will not lose anything, though you may be asked to sign in to Cartographer again.
What Changed
- Structured results. Every tool now publishes an output schema next to its input schema and returns its result as structured data, not a block of JSON text. Your AI knows the shape of a result before it calls a tool. The MCP server page has an example response.
- Readable titles and safety hints. Each tool has a readable title, like “Create story card”, and is marked as read-only or destructive. Clients use this to label tools and to decide when to ask you first, for example before deleting a card.
- Sign-in discovery. The server now publishes OAuth protected resource metadata, as the spec requires. Clients find where to sign in without guessing, so connecting a new client is more reliable.
- Name and icon. The server tells clients its name, logo and website, so Cartographer shows up with its logo in clients that display them.
Still Stuck?
If Cartographer still does not work after reconnecting, email support@cartographer.studio and tell us which AI tool you use. We will help you get it running.
