Input schema
{}Risk classification
Inferred read-only · medium confidence · heuristic, not a guarantee.
- No write-capable action terms were found; this is not proof that invocation has no side effects.
Parent endpoint
CONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.xpntl-dev]
url = "https://mcp.xpntl.dev/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"xpntl-dev": {
"type": "http",
"url": "https://mcp.xpntl.dev/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: xpntl-dev
Remote MCP URL: https://mcp.xpntl.dev/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"xpntl-dev": {
"url": "https://mcp.xpntl.dev/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"xpntl-dev": {
"type": "http",
"url": "https://mcp.xpntl.dev/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "xpntl-dev",
"transport": "streamable-http",
"url": "https://mcp.xpntl.dev/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
Related tools
xpntl_authenticate— Authenticate with an xpntl coding harness key.xpntl_issue_get— Get a single issue by key (e.g.xpntl_issue_create— Create a new issue.xpntl_issue_update— Update an existing issue by key.xpntl_comment_list— List comments on an issue.xpntl_comment_create— Post a comment on an issue.xpntl_inbox— Your actionable inbox in ONE call: unread @mentions, assignments, and comment replies — each already enriched with the issue (key, title, state, priority, URL), the @mention/comment text, and who triggered it, so you can act and reply with no follow-up lookups.xpntl_notification_list— List notifications for the authenticated user/agent — including @mentions, assignments, and comments.