Planned agent plugin
Bring Planned into your agent through one MCP server, so you can work with your events without leaving the tool you are already in.
What it does
The plugin connects your agent to Planned's client-facing MCP server. Planned serves its multi-tool workflows through the read-only load_skill tool, so every client receives current instructions without a plugin update.
| Workflow | What it does |
|---|---|
where_to_meet_workflow | Recommends or compares meeting cities for a distributed team, and can hand the city you pick into event creation. |
payment_facilitation_workflow | Prepares and confirms a payment facilitation request from a contract, resolving or creating and publishing the exact event first. |
event_creation_workflow | Creates one event or completes and publishes an existing draft, including company intake questions. |
Everything the plugin can do runs through the Planned MCP server, acting as the Planned user who authorized the connection. The package itself is manifests, Markdown, and an icon — it ships no executable code.
Install
In Claude Code:
/plugin marketplace add planned-inc/agent-plugin
/plugin install planned@planned
In Codex:
codex plugin marketplace add planned-inc/agent-plugin
codex plugin add planned@planned
Codex reads .agents/plugins/marketplace.json, .codex-plugin/plugin.json, and .mcp.json from this repository.
The first run opens a browser to sign in with Planned. Nothing works until that completes.
Requirements
The plugin installs none of these.
- A Planned account that is an active client user, belonging to a single company. Which events you can reach follows your role.
- A browser, to complete the OAuth sign-in — including your company's SSO where it applies.
- An agent client that supports plugins and HTTP MCP servers.
No runtime, package manager, or CLI binary is needed. There is no build step and no dependencies.
What it accesses
- One network host:
https://mcp.planned.com/mcp, over HTTPS, whenever a Planned tool is called. Signing in additionally opens Planned's own web sign-in. - The contract file you supply for payment facilitation. In Codex, the agent may read that local file and send its bytes to Planned through the authenticated MCP call. It does not need access to unrelated files. In ChatGPT, the host supplies the attachment through a temporary download URL instead. The plugin itself still has no hooks, scripts, or executable files.
- No credentials of its own. Authentication is OAuth 2.1 with PKCE, negotiated between your client and Planned, requesting the
mcp.readandmcp.writescopes. Planned shows you the scopes before you allow the connection. Tokens are held by your agent client, not by the plugin. - No telemetry. The plugin collects nothing and reports nothing; it ships no code that could. Tool calls you make do reach Planned's servers, which handle them like any other authenticated Planned request.
Full details, including every tool the workflows call, are in the documentation.
Contact
- Support — support@planned.com
- Security — security@planned.com
License
No license is declared for this plugin.