MCP

Connect PSPO Agent to the CLI you already use

Available in private beta

You can now use PSPO Agent through a remote MCP server designed for Codex CLI, Codex IDE, Claude Code and Gemini CLI.

We do not expose the raw backend. We wrap the real product flow into high-level tools: create projects, attach documentation, import stories, resolve clarifications and prepare backlog plus actionable delivery documentation.

Remote MCP over HTTP.
API-key based authentication.
Public REST for binaries, Jira and backends.
Request priority access View in-app setup

How the setup works

Connect it once, then ask your agent to run the full flow from your terminal or IDE.

Paso 1

Generate your API key

Each user creates their own keys from the SaaS and can revoke them per client or environment.

Paso 2

Paste the snippet

We provide the official URL and ready-to-use blocks for Codex CLI, Codex IDE, Claude Code and Gemini CLI.

Paso 3

Work with your agent

Ask it to analyze requirements, generate user stories, resolve clarifications and prepare delivery.

Clients we are actively supporting

The MCP is designed to fit the CLI or IDE your team already uses.

Codex CLI

Great if you already work from the terminal and want one instruction to trigger the full flow.

Codex IDE

Same remote endpoint to use PSPO Agent from the graphical environment without duplicate setup.

Claude Code

Remote HTTP MCP server with high-level tools for backlog, clarifications and delivery.

Gemini CLI

Remote configuration with token-based auth and tools designed for real documentation workflows.

What happens when your agent calls PSPO Agent

Your agent does not need to understand our internal endpoints. It only calls tools that wrap the real SaaS workflow.

Provide documentation or stories

It can start from text, URL or approved stories coming from Jira or another system.

PSPO analyzes and detects gaps

If context is missing, it returns structured clarifications so the agent only asks what is necessary.

Generate backlog and delivery

Once the base is strong enough, it prepares stories, dependencies, planning and engineering artifacts.

Return artifacts and exports

The agent can read results and download Markdown, PDF or ZIP for sharing or attachments.

REST and MCP, each in the right place

The right integration separates transactional work from agent orchestration.

Public API v1

For Jira, Confluence, internal backends, binary uploads and system-to-system automation.

  • Document and text uploads.
  • Ingestion by URL.
  • Import of approved stories.
  • ZIP, Markdown and PDF downloads.

MCP server

For agents and CLIs. It wraps business logic into better tools for backlog and actionable delivery documentation.

  • High-level tools.
  • Structured clarifications.
  • Shared context for product and engineering.
  • Less friction for the end user.

What it can already do

The remote MCP server is already geared toward helping an agent with the work that happens before development starts.

  • Create draft projects and activate them with the first useful content.
  • Attach documentation by text or URL.
  • Import approved stories from other systems.
  • Read and answer clarifications.
  • Generate delivery documentation in a single flow.
  • Read artifacts and export the full package.

Built to fit your real workflow

It does not force your team into a new tool or process. We designed it to work well with the CLI you already use, while keeping the public REST API as the right layer for transactional work.

  • It keeps product and engineering in the same shared context.
  • It fits Codex, Claude Code and Gemini CLI without brittle setup.
  • It keeps the public REST API as the right base for attachments, PDFs and external systems like Jira.
  • It lets an agent trigger backlog and actionable delivery documentation from one place.
  • Dedicated endpoint: mcp.pspo-agent.com.

Current status

The public API v1 is already hardened, the remote MCP server is live on its own subdomain, and the setup is available inside the SaaS with per-client snippets.

Designed for the agent you already use

If your workflow lives in Codex, Claude Code or Gemini CLI, the MCP lets you call PSPO Agent without homemade integrations or brittle setup. And if you need binaries or Jira connectivity, the public REST API remains the right foundation.

Request priority access View in-app setup