paymo-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PAYMO_TOOLS | No | Comma-separated tool names, additive on top of the toolsets. Matched exactly as registered. | |
| PAYMO_API_KEY | Yes | Paymo API key used with HTTP Basic auth. Required. | |
| PAYMO_BASE_URL | No | API base URL. Default: https://app.paymoapp.com/api | https://app.paymoapp.com/api |
| PAYMO_TOOLSETS | No | Comma-separated toolset names, plus the keywords default and all. Case-insensitive and whitespace-tolerant. Default: default | default |
| PAYMO_READ_ONLY | No | Deprecated. Use PAYMO_PERMISSION_MODE. true maps to readonly, false to modify. | |
| PAYMO_STATUS_ALIASES | No | JSON object overriding status aliases, e.g. {"wip":123,"done":456}. Keys are slugified, values must be positive integers. | |
| PAYMO_PERMISSION_MODE | No | One of readonly, modify, full. Default: modify | modify |
| PAYMO_DEFAULT_PROJECT_ID | No | Project used when a project id argument is omitted. | |
| PAYMO_DENIED_TOOLS_REGEX | No | One JS regex, matched against tool names and subtracted from the resolved set last. |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| paymo_meA | Returns the authenticated Paymo user (id, name, email, timezone, workflows, assigned projects). |
| paymo_list_workflow_statusesA | List the workflow statuses available in Paymo (id, name, seq, action) — useful to map status_id to a human name. |
| paymo_list_projectsA | List Paymo projects the user has access to, with the documented field subset. |
| paymo_list_tasklistsA | List tasklists (columns) for a project, or across all tasks when unset. |
| paymo_list_tasksB | List tasks, defaults to incomplete tasks of the configured project. |
| paymo_get_taskA | Fetch a Paymo task by numeric id or human code. |
| paymo_create_taskA | Create a new Paymo task. Requires a name and either a project_id or a tasklist_id. Optional: description, due_date (YYYY-MM-DD), priority (100/75/50/25), users (list of user ids). |
| paymo_update_taskA | Update a Paymo task. status accepts a numeric id or a slug alias (e.g. in_progress). Do not send complete and status together: Paymo forces the status to Complete when completing and to Backlog when reopening, so the status argument would be overwritten. |
| paymo_add_commentB | Add a comment to a Paymo task. |
| paymo_timer_statusA | Returns the running Paymo time entry for the authenticated user, or null if no timer is active. |
| paymo_start_timerA | Start a running Paymo time entry on a task. Any running timer for the user is closed first to avoid concurrency. |
| paymo_stop_timerA | Stop the running Paymo time entry of the authenticated user. No-op if none is active. If the entry is under a minute old Paymo may refuse the stop; delete it with paymo_delete_entry instead. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Gestazion2023/paymo-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server