# Padlet MCP connector

The Padlet connector lets Claude, ChatGPT, Cursor and the Elaichi Agent create padlets, read and edit posts and comments, and manage sharing, with each person signed in as themselves and every change written to an audit log.

Source: https://elaichi.ai/connectors/padlet/

## Facts

| | |
| --- | --- |
| Application | Padlet |
| Category | Knowledge Management |
| Authentication | Connects over OAuth |
| Bring your own OAuth app | No |
| Native MCP | Yes. Padlet builds and runs this MCP server. Elaichi adds sign-in, access controls and an audit log on top |
| Support for its tools | padlet.help |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Padlet is connected

- Summarize the new posts on the Q3 planning padlet since Monday.
- Create a padlet for next week's onboarding cohort with four sections.
- Which comments on the feedback board still have no reply?

## Connect Padlet in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Padlet.
2. Optionally set Share with, then press Connect.
3. Approve it in Padlet. Padlet's own window opens. Whoever approves it decides what this connection can reach.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Padlet tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Padlet MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## Padlet MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

## Padlet MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Connect Padlet to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Only Read is granted by default, which is not enough to call a Padlet tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone.

## What teams do with Padlet through Elaichi

### Summarize what students posted this week

Teaching. Ask for a rundown of new posts on a class padlet since Monday and which ones still have no comment from you. Reply to the quiet corners of the board without scrolling through all of it.

### Build a course board in one ask

Training. Describe a new cohort and get a padlet with the sections, welcome post and sharing settings your training program always uses, ready before the first session.

### Keep the onboarding board current

HR. Move stale posts, update the start-date checklist and invite new hires to the onboarding padlet from one request, so nobody arrives to last quarter's instructions.

### Turn an idea board into a shortlist

Marketing. Pull every post from a campaign brainstorm padlet, group them by theme and get a shortlist with the comments that backed each idea.

### Catch the agenda up after a change

Events. When a speaker drops or a room moves, edit the agenda posts on the event padlet and add a comment so attendees see the change where they already look.

### Review who can see which padlets

IT. List the padlets shared outside the organization, tighten sharing settings and run routine admin tasks on the Padlet account without clicking through each board.

## Elaichi vs Zapier MCP vs Composio for Padlet

All three can connect Padlet 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. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Padlet tools | Allow or restrict single Padlet 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 Padlet 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 | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect Padlet to Claude?

In Elaichi, choose Padlet and connect it; Padlet's own sign-in screen opens, you approve access, and you are done. There is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint.

### Does Padlet work with ChatGPT and Cursor as well as Claude?

Yes. Once Padlet is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect Padlet once and every client you use picks it up.

### What can an AI agent actually do with my Padlet data?

With Padlet connected, an agent can create padlets, read and edit posts and comments, change sharing and settings, and run admin tasks on your account. In practice that means asking for a summary of this week's posts, setting up a board for a new cohort, or tightening who can see a padlet. Short, concrete asks such as "list unanswered comments on the feedback board" work better than long paragraphs.

### Does connecting Padlet give the AI everything in my workspace?

No. Access to Padlet follows the person who signed in, so the agent sees only the padlets, posts and comments that person can already open. Elaichi can narrow that further with roles and restrictions, and it never widens it beyond what Padlet itself allows.

### Can my team share one Padlet connection?

Yes. One person connects Padlet in Elaichi and shares the connection with a team, and nobody else ever handles a credential. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every change to a padlet.

### Can I stop an agent from deleting or changing things in Padlet?

Yes. Restrictions in Elaichi apply per action, so you can allow reading posts on Padlet while blocking edits, deletions or changes to sharing. A restricted action is never advertised to Claude, ChatGPT or Cursor at all, so no prompt can reach it.

### What happens to a Padlet connection when someone leaves?

Offboarding a person in Elaichi ends their access to Padlet through every client at once. If they had shared a Padlet connection with a team, it keeps working for everyone else. Disconnecting Padlet once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client together.

### Does the Padlet MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Padlet 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, 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 Padlet?

Yes. Both let Claude, ChatGPT or Cursor use Padlet. 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 Padlet call.

### How is Elaichi different from Composio for Padlet?

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 Padlet: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.