Connect your agent to Pachca
Ask Claude, ChatGPT or Cursor to find what you agreed with a customer, sum up a discussion or tell teammates what got done. The agent pulls the details it needs straight from your Pachca chats.
For apps that support MCP.
Look through my Pachca chats for the last three days. Tell me what I missed and where people are waiting on me.
Pachca: 4 chats, 38 messages, 5 threads
Everything that matters is in the Backend chat. Nothing urgent in the other three.
Shipped: release 3.2 went out on Monday, no errors since.
Fixed: report export was failing on files over 50 MB, Daniel now builds them in chunks.
Moved: the Romashka call is now Friday at 12:00.
Waiting on you
Emily: review of the payments PR, she's unsure about the card check.
Daniel: review of the export PR.
Backend
9 members
Release 3.2 is out, shipped at 9:40. All quiet so far, watching monitoring.
Caught a bug in report export: it fails on files over 50 MB. Log in the thread.
when you’re back, take a look at the payments PR. It’s your code and I’m not sure about the card check.
The Romashka call moved to Friday, 12:00.
Fixed the export: building the file in chunks now. PR in the thread, need your review.
Romashka asked about Excel export. Told them it's planned for 3.3.
What to hand to an agent over MCP
What did we agree with Romashka on the rollout timeline? Search the chats for the last month
Found it in the Romashka · rollout chat: the pilot is 50 people from Nov 3, SSO comes after the pilot, full migration by year end and not in the contract yet.
Romashka · rollout
6 members
Agreed with Romashka: the pilot is 50 people, starting Nov 3.
SSO goes after the pilot. Their requirements are in the file.
Full migration by year end. Not in the contract yet, discussing in the thread.
How to connect an agent to Pachca
Pick the app you use with your agent and follow the steps.
1. Add Pachca's MCP server
Add the MCP server in the settings of the app you use with your agent.
https://mcp.pachca.com/mcp- Open Customize → Connectors and click “Add custom connector”
- Name: Pachca, URL: https://mcp.pachca.com/mcp
- Allow access on the Pachca screen. In a chat, turn the connector on via “+” → Connectors
2. Allow access to Pachca
Pachca shows which app is asking for access, to which workspace and with what permissions. If it all checks out, click Allow.
If you connect with a token, there is no Pachca sign-in page. See the “Other app” tab for the steps.
You control what the agent can access
- Access within your role
- Connected on your behalf, the agent sees only the chats and threads you can see. Pachca checks permissions on every action. With a bot token, the bot's permissions apply.
- Confirmation before sending and deleting
- In the app you use with your agent, turn on confirmation before sending and deleting messages. That way you stay in control of every important action the agent wants to take.
- Access can be revoked
- Revoke access under Authorizations on the API page. Every connection of that app loses access to Pachca.
API / Authorizations
- Revoke
Claude CodeMCP client
claude.ai · connected Oct 21
- Revoke
CursorMCP client
cursor.com · connected Oct 21
Questions about connecting
What data does the agent get?
How is this different from an AI agent in threads?
What if a chat contains commands for the agent?
Can I connect with a token?
Connect an agent to Pachca
Add the MCP server to your app and give the agent its first task. For example, ask it to find what was agreed in a work chat.
https://mcp.pachca.com/mcp