Podio MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port for HTTP/SSE mode (e.g. PORT=3016) | 3016 |
| clientId | Yes | Podio API client ID (required; set in podio.config.json) | |
| password | No | Podio password (optional; set in podio.config.json) | |
| username | No | Podio username (optional; set in podio.config.json) | |
| BIND_ADDRESS | No | Bind address for HTTP/SSE mode (e.g. BIND_ADDRESS=0.0.0.0) | 0.0.0.0 |
| clientSecret | Yes | Podio API client secret (required; set in podio.config.json) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| podio_itemsC | Manage Podio items: fetch, create, update, delete, and filter items in apps. |
| podio_apps_spacesC | Manage Podio Spaces, Apps, and Organizations, including activity streams. |
| podio_tasksC | Manage Podio tasks: fetch, create, update, and complete tasks. |
| podio_communicationC | Manage comments, statuses, notifications, tags, and subscriptions. |
| podio_searchC | Search across Podio for items, tasks, statuses, contacts, etc. |
| podio_metadataC | Explore Podio API, app fields, app relations (direct or deep to max depth), forms, and views. |
| podio_systemD | System tools: ping, config, files, hooks, batch, and calendar. |
| callPodioApiB | Call any Podio API endpoint from the catalog. Use getApiDetails to see available endpoints and their parameters. Example: "call the items-get endpoint with item_id 123" |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
The tools are mostly separated by Podio domain (items, tasks, search, communication, metadata), so an agent can usually pick the right category. However, callPodioApi overlaps with every other tool as a generic catch-all, and boundaries such as items-filtering versus search are somewhat loose.
Seven tools follow a clear podio_<domain> snake_case convention, but callPodioApi breaks the pattern with camelCase and no podio_ prefix. The set remains readable, but the convention is not fully consistent.
Eight tools is a well-scoped count for a broad API like Podio, with each major domain area represented without excessive fragmentation. The domain-bundle approach keeps the count manageable while still exposing the main capabilities.
The surface covers the major Podio areas: items, apps/spaces/organizations, tasks, communication, search, metadata, and system utilities. The generic callPodioApi tool also provides an escape hatch for any endpoint not explicitly bundled, so there are no obvious dead ends.