MCP - Use Picasi in the AI assistant
What MCP Is
The Model Context Protocol (MCP) is an open protocol that defines how AI assistants access external tools and data. Instead of each provider having to build its own integration, everyone follows the same standard.
Claude Code, Claude.ai, ChatGPT, and other assistants that support MCP can connect to any MCP-compatible service—and Picasi is one of them.
Why Picasi Implements MCP
Competitive monitoring becomes truly useful when the information is available right where you work—not in a separate app that you have to open just for that.
If you’re writing a competitive analysis in Claude and want to know in the middle of your work what Muster AG communicated last week, just ask Claude. Claude queries Picasi via MCP in the background—and you see the data immediately in the chat without switching contexts.
That’s the real advantage of MCP: Picasi data flows into your existing AI workflow instead of forcing you to use a separate one.
How the connection works
There are two ways to connect Picasi to an AI assistant:
API token — for Claude Code, Cursor, and your own agents. You create a token in Picasi, enter it into the assistant’s configuration, and it has access right away. The token has a role that determines the scope of access.
OAuth — for Claude.ai and ChatGPT. You authorize the assistant directly through your Picasi account, without token management. The connection is tied to your personal account.
What the assistant can do
With read access, the assistant can:
- Search for and read updates
- List sources and channels
- Retrieve reports
- Query the team context (AI context)
With write access (admin token or OAuth with write scope), the assistant can additionally:
- Create, edit, and delete sources
- Create, edit, and deactivate channels
- Create and edit tags
Security and Control
You remain in control. Every connection is visible in Picasi under Settings → AI Connections and Tokens. You can revoke them individually at any time—immediately and without any lingering effects.
Tokens are role-restricted: a reader token cannot create sources, regardless of how the assistant uses it.