Using AltStudio in Claude
AltStudio exposes its own MCP server, so you can connect your workspace to Claude (or any MCP client) and work with your real context — canvases, knowledge, entities, reference files, and data — right there.
The other pages in this section are about connecting external tools into AltStudio. This one is the reverse: AltStudio exposes its own MCP server, so you can connect your AltStudio workspace to Claude — or any MCP client — and bring your real context into that tool.
Your work doesn't stay locked in one app. Connect AltStudio in Claude and you can search your workspace, pull up a canvas, look up what you know about a company, read a report you wrote, or query a dataset — without leaving the conversation.
Connecting AltStudio
Add AltStudio as a connector in your MCP client and point it at AltStudio's MCP endpoint:
https://www.altco.ai/mcpAdd the connector
In Claude, open your connector settings and add a custom connector, using the URL above. (Any MCP client works the same way — give it that endpoint.)
Authorize it
You'll be sent to sign in to AltStudio and approve access. This uses your own AltStudio account, so the connection gets exactly the access you already have.
Work with your workspace
Once connected, the client can search your workspace, open canvases, look things up in your knowledge graph, read your reports, and query your data — and write back where it makes sense.
Everything runs as you, with your permissions. The connection uses your own sign-in, so a client only ever sees what you could see in AltStudio — and writes are made under your account. Nothing is exposed that you don't already have access to.
What you can bring in
Once connected, the client can read across your workspace:
- Search your workspace in natural language, and pull recent activity.
- Canvases — list them, open one, and read its nodes and a summary.
- The knowledge graph — look up entities (people, companies, topics) and their facts and connections.
- Reference files — find and read the documents and reports in your store.
- Data — list your data sources and run filtered, sorted, and aggregated queries against them.
There's also a one-step "load my AltStudio context" starter that pulls your active workspace's brand, recent work, and key entities into the conversation, so the client is working from your real data straight away.
What it can write back
Where it makes sense, the client can also create in your workspace:
- Author a reference file — write a report or note (markdown, and other formats) straight into your store, where it becomes a first-class, citable item.
- Build and update data — create a data source, add rows, and update records.
Destructive actions — deleting a record or a whole data source — are marked as such, so a client can prompt you before running them; and only the owner of a data source can delete it.
Why it matters
The point of AltStudio's context — your canvases, your knowledge graph, your reports and data — is that it's yours and it's structured. Exposing it over MCP means that context travels with you: the work you do in AltStudio is available wherever you work, and work you do elsewhere can flow back in.