axiom-zen-mcp.yml

Endpoint

Hosted endpoint · transport

Connect

This is a remote MCP server — point an MCP client at the endpoint URL. Clients with native remote support (Claude, Cursor, VS Code, …):

For stdio-only clients (older Claude Desktop, etc.), bridge with mcp-remote:

If the server requires authentication, add the provider's token/header (e.g. an X-API-Key) per its docs. A quick reachability check:

Tool quality observed · not scored

Unhinted state-changing: createZenhubIssue, createGitHubIssue, addIssuesToSprints, removeIssuesFromSprints, assignIssues, createBlockage, setDatesForIssue, setParentForIssues …

From an anonymous initialize + tools/list capture measured 2026-10-20; tokens are chars/3.6 of each tool definition. Recorded for the Kin Score's agent readiness as an observed signal — it contributes no points yet.

Tools

• getWorkspacePipelinesAndRepositories — Get a list of all pipelines for the current workspace
• getTeamMembers — Get a list team members in the workspace. This will include their zenhub user ids and github usernames, if applicable. The viewer refers to the person who ran the command.
• searchLatestIssues — Get the latest 20 issues from Zenhub. Can optionally pass a search query to filter the results.
• searchClosedIssues — Search closed issues in the workspace. Can optionally pass a search query and filters.
• getIssuesInPipeline — Get a list of all issues in a specific pipeline. Useful for getting issues that are in progress, in review, iceboxed, or needing triage. Provide all of the repository ids in the workspace.
• getSprint — Get the issues, dates, and metadata for a sprint. If no sprintId is provided, returns the active sprint. Issues with a CLOSED state are completed.
• getUpcomingSprint — Get the issues, dates, and metadata for the next sprint in this workspace. Issues with a CLOSED state are completed.
• listRecentSprints — Get the last 10 open and last 10 closed sprints in the workspace, returning their name and id.
• createZenhubIssue — Create a new Zenhub issue. These are used to track work, and are especially useful for tasks that aren't linked to GitHub. Zenhub issues can not have GitHub issues as their parents. repositoryId should be the graphql id of the workspace's zenhubRepository.
• createGitHubIssue — Create a new issue on GitHub. These are used to track work, generally for developer-focused tasks. repositoryId should be the graphql id of one of the githubRepositories on the workspace. assignees should be an array of github usernames (without the @)
• addIssuesToSprints — Add issues to sprints
• removeIssuesFromSprints — Remove issues from sprints
• assignIssues — Assign one or GitHub issues to one or more people. assigneeIds should be github user ids
• createBlockage — Create a blocking dependency relationship between two issues
• setDatesForIssue — Set start and end dates for an issue. This should only be used for Epics, Projects, Initiatives, or other high-level issue types. Dates should be provided in YYYY-MM-DD format, eg "2025-10-28". Use getWorkspacePipelinesAndRepositories to get the zenhubOrganizationId. To clear dates, pass null for both startDate and endDate
• setParentForIssues — Create a sub-issue relationship between a parent and one or more child issues, using their graphql issue ids
• moveIssueToPipeline — Move an issue to a specific pipeline
• setIssueEstimate — Set the estimate for an issue in story points or hours
• getIssueTypes — Get all available issue types in the workspace.
• setIssueType — Set the issue type for one or more issues.
• updateIssue — Update an existing Zenhub or GitHub issue. Only provide the optional issue fields that you need to change. To close an issue, set state to "CLOSED"

About MCP

The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.

Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.

Work with this as data

Every MCP server here is available over the APIs.io API and to AI agents over MCP.

curl "https://apis.io/api/v1/mcp/axiom-zen-mcp-yml"

curl "https://apis.io/api/v1/mcp?limit=25"