Connect your tools via MCP.

What you need.

A Tonika workspace on a Solo plan or above. An MCP-compatible tool (Claude Desktop, Cursor, Windsurf, or any client that supports the protocol).

Setup.

1. Go to your workspace settings.
2. Generate an MCP API key. Each workspace gets its own key.
3. Copy the MCP server URL shown on the settings page.
4. Open your tool's MCP configuration. In Claude Desktop, this is Settings → Developer → MCP Servers. In Cursor, this is Settings → MCP.
5. Add a new server. Paste the URL. Save.
6. Done. Your next session in that tool pulls your brand context on demand.

What your tools can pull.

1. Workspace overview. Summary of your brand context and what each library contains.
2. Library contents. All records in a specific library (voice, positioning, messaging, etc.).
3. Individual records. A single brand directive, definition, or spec.
4. Full-text search. Find any term, phrase, or concept across your entire brand context.
5. Export-ready prompt blocks. Pre-formatted brand context optimized for AI tool consumption.
6. Complete brand context dump. Everything in one pull.

Supported tools.

Any tool that supports Model Context Protocol can connect to Tonika. Currently tested and confirmed:

• Claude Desktop
• Cursor
• Windsurf
• Every MCP-compatible client

Troubleshooting.

Tool isn't pulling brand context.

Check that the API key is active and the server URL is correct. Regenerate the key if needed.

Getting stale data.

MCP pulls are live. If data seems stale, check that you saved your changes in Tonika. The tool pulls whatever is current at the moment of the request.

MCP option not available in my tool.

Your tool may not support MCP yet. Use structured exports instead. Check your tool's documentation for MCP support.