Penneo MCP connector
The Penneo connector lets Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent create casefiles, build and publish forms, and read submissions and answers in Penneo, with every action running as the signed-in person and recorded in an audit log.
- Connects over OAuth
- Free 14-day trial
- No credit card
Which Penneo casefiles are still waiting on signatures?
Working in Penneo with Elaichi
-
List all Penneo oauth
-
List all Penneo version
-
List all Penneo casefile answers
How to connect Penneo to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Penneo MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Penneo MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Penneo MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web. The plugin directory lives at chatgpt.com/plugins.
Penneo MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Penneo MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect Penneo to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with Penneo through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Penneo is logged.
-
Legal
Open a casefile for a new agreement
Ask for a Penneo casefile to be created for a supplier agreement or NDA, then check which files it holds before anyone is asked to sign.
-
HR
Build and publish an onboarding form
Draft an onboarding form in Penneo from a description of the fields you need, publish the version, and send a form request to each new starter.
-
Sales
Get a contract signed after the close
When a deal closes, have a Penneo casefile created for the customer contract in the same conversation, without opening another tab.
-
Compliance
Review what people actually submitted
Pull the answers from a Penneo form's submissions and have them summarized, so you can spot missing declarations before the deadline.
-
Operations
Update a form and roll back safely
Change a Penneo form, publish the new version, and restore the previous one if something is wrong, all by asking in plain language.
-
Finance
Check answers on signed casefiles
Ask which casefile answers came back for an approval or expense form in Penneo, and get a clean list rather than clicking through each one.
Try asking
- “Which Penneo casefiles are still waiting on signatures?”
- “Show form requests created this week and their answers.”
- “List every Penneo form used by the onboarding team.”
What connecting Penneo gets you
6 screens from Elaichi, each doing one job for your Penneo account.
Ask Elaichi to work across your apps.
Which Penneo casefiles are still waiting on signatures?
Show form requests created this week and their answers.
List every Penneo form used by the onboarding team.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about casefiles, get real answers.
Type a question in plain language and read live Penneo casefiles and forms.
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot reach Penneo.
One org MCP endpoint over OAuth, no SDK and no shared API key.
Tool catalog
All 22 Penneo tools, ready to call.
Browse casefile, form and form request methods without writing custom code.
Toolboxes
Every team gets its own Penneo toolbox.
Curate one toolbox per team so Legal and Finance see different Penneo tools.
Shared connections
Teammates use Penneo without a credential.
See who connected each Penneo account and which teams and members share it.
Audit log
Every Penneo call is on the record.
When, who, what happened, type and resource for each casefile and form request.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
Penneo digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch casefiles
Penneo
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Penneo
Queued
Automations
A schedule signs off your signing digest.
Fetch Penneo casefiles, group them, draft a digest, approve, post it back.
Penneo health
Refreshed 4 minutes ago · every 15 minutes · from the casefiles collection
Casefiles
1,284 ↓ 12%
Forms
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Casefiles created
Last 14 days
By team
Share of activity
Legal Nordics 34%
Finance 27%
HR Onboarding 21%
Sales EMEA 18%
Collections and dashboards
Penneo signing health, refreshed on schedule.
Four metrics, 14 days of casefiles created and a breakdown by team.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Penneo
All three can connect Penneo to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Penneo tools | Allow or restrict single Penneo tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Penneo call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
Penneo tools for your AI agents
22 tools are ready to call through Elaichi's MCP endpoint the moment you connect Penneo, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
How do I connect Penneo to Claude?
Connect Penneo in Elaichi first, then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Penneo connects over OAuth, but Penneo requires the customer to register an OAuth application inside Penneo themselves, so one person enters that client ID and secret in Elaichi once. After that, everyone else simply signs in to Penneo in a normal browser window when Claude first asks.
Does Penneo work with ChatGPT and Cursor as well as Claude?
Yes. Penneo is connected once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, is pasted into Claude, ChatGPT, Cursor, Microsoft Copilot or any other MCP client. The Elaichi Agent uses it too, so nobody sets Penneo up twice.
What can an AI agent actually do with my Penneo data?
With Penneo connected, an agent can create a casefile for a document that needs signing, list the files and answers on a casefile, and build, update, publish, archive or restore forms. It can also send a form request to someone and read back the submissions and answers they return, so you can ask questions like who has not yet filled in the onboarding form.
Does connecting Penneo give the AI access to all my casefiles and forms?
No. Every call to Penneo runs as the person who signed in, so the AI sees only the casefiles and forms that person could already open in Penneo. Elaichi can narrow that access further, for example by restricting delete actions, but it can never grant more than the person already has.
Can I stop an agent from deleting or changing things in Penneo?
Yes. Restrictions in Elaichi apply per action, so you can allow reading Penneo submissions while restricting form deletion or version changes. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor or Microsoft Copilot cannot run it, whatever the prompt says.
What happens to a Penneo connection when someone leaves?
Offboarding a person in Elaichi ends their access to Penneo through every client at once. A Penneo connection shared with a team keeps working for everyone else. If you want Penneo gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent together.
Does the Penneo MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Penneo is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Penneo?
Yes. Both let Claude, ChatGPT or Cursor use Penneo. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Penneo call.
How is Elaichi different from Composio for Penneo?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Penneo: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Penneo in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot