← All Docs

Integrations

PM MCP Server

Webase exposes a public PM MCP server for project and feature management. This page is generated from the live tool classes in the app, so the tool list below reflects the MCP surface that is actually registered in production code.

Server: webase-pm v1.0.0

Endpoint: https://www.webase.com/mcp/pm/messages

Protocol: JSON-RPC over HTTP using MCP tools/list and tools/call.

Authentication

The public path uses OAuth. Internal agent clients can also authenticate with an x-api-token header, but that is not the recommended public integration path.

Authorization URL — https://www.webase.com/oauth/authorize
Token URL — https://www.webase.com/oauth/token
Authorization Metadata — https://www.webase.com/.well-known/oauth-authorization-server
Protected Resource Metadata — https://www.webase.com/.well-known/oauth-protected-resource
Scopes — pm_read, pm_write, offline_access

Tool Summary

The current PM MCP server exposes 13 tools. Read tools require pm_read or pm_write. Write tools require pm_write.

append_implemented_summary WRITE

Use this after implementation work ships to append a concise summary of what was delivered to the project's implemented summary.

Input schema

project_id_or_slug Required string

Project identifier. Accepts either the numeric id or the friendly slug.

text Required string

Summary text to append to the implemented summary.

claim_next_feature WRITE Destructive

Use this in an automated implementation loop to atomically reserve the next ready, unblocked feature for a project and mark it running for the current agent.

Input schema

project_id_or_slug Required string

Project identifier. Accepts either the numeric id or the friendly slug.

agent_name string

Optional agent name to record on the claimed feature, such as codex.

complete_feature WRITE Destructive

Use this after implementation is verified to mark a feature done, record completion metadata, and clear it from the active execution queue.

Input schema

feature_id_or_slug Required string

Feature identifier. Accepts either the numeric id or the friendly slug.

agent_name string

Optional agent name to record on the completed feature, such as codex.

create_feature WRITE

Use this to create a new feature in a project after checking project context and existing features. Do not use it to update an existing feature.

Input schema

project_id_or_slug Required string

Project identifier. Accepts either the numeric id or the friendly slug.

title Required string

Short feature title.

description Required string

Detailed feature description for planning and implementation.

priority string

Optional priority. Allowed values: low, medium, high, urgent.

Allowed values: low, medium, high, urgent

roadmap_bucket string

Optional roadmap bucket. Allowed values: now, next, later.

Allowed values: now, next, later

depends_on_feature_id null | integer

Optional dependency feature id in the same project. Use null to omit any dependency.

get_feature READ

Use this to fetch the full feature record when you need current implementation status, dependency state, or detailed feature content.

Input schema

feature_id_or_slug Required string

Feature identifier. Accepts either the numeric id or the friendly slug.

get_next_feature READ

Use this when an implementation agent needs the next ready, unblocked, non-running feature for a project. Returns the selected feature plus project context.

Input schema

project_id_or_slug Required string

Project identifier. Accepts either the numeric id or the friendly slug.

get_project READ

Use this to fetch the full project record when you need project metadata such as name, key, status, description, context, or implemented summary.

Input schema

project_id_or_slug Required string

Project identifier. Accepts either the numeric id or the friendly slug.

get_project_context READ

Use this when you need project memory for planning or implementation. Returns only the project context and implemented summary.

Input schema

project_id_or_slug Required string

Project identifier. Accepts either the numeric id or the friendly slug.

list_features READ

Use this to list all features for a specific project before reading one in detail, updating one, or proposing new work.

Input schema

project_id_or_slug Required string

Project identifier. Accepts either the numeric id or the friendly slug.

list_projects READ

Use this to list the current user's projects before selecting one to inspect, update, or create features in. Returns only a small project summary.

Input schema

This tool takes no arguments.

search_project_memory READ

Use this to search project memory for prior decisions, shipped work, implementation notes, and related features before proposing or creating new work.

Input schema

project_id_or_slug Required string

Project identifier. Accepts either the numeric id or the friendly slug.

query Required string

Plain-text search query used against project context, implemented summary, and feature title, description, implementation plan, implementation summary, and failure summary.

update_feature WRITE Destructive

Use this to update an existing feature's planning or execution fields such as title, description, implementation plan, implementation summary, failure summary, status, priority, roadmap bucket, or dependency.

Input schema

feature_id_or_slug Required string

Feature identifier. Accepts either the numeric id or the friendly slug.

fields_to_update Required object

Hash of feature fields to update. Provide only the fields that should change.

Field	Type	Description
`title`	string	Updated feature title.
`description`	string	Updated feature description.
`implementation_plan`	string	Working implementation plan recorded by the agent during execution.
`implementation_summary`	string	Concise summary of what was implemented for this feature.
`failure_summary`	string	Concise summary of why implementation failed or what remains blocked.
`development_started_at`	string	When development began for this feature. Use an ISO 8601 timestamp.
`development_completed_at`	string	When development finished for this feature. Use an ISO 8601 timestamp.
`status`	string `backlog`, `ready`, `in_progress`, `in_review`, `done`, `canceled`	Updated status. Allowed values: backlog, ready, in_progress, in_review, done, canceled.
`priority`	string `low`, `medium`, `high`, `urgent`	Updated priority. Allowed values: low, medium, high, urgent.
`roadmap_bucket`	string `now`, `next`, `later`	Updated roadmap bucket. Allowed values: now, next, later.
`depends_on_feature_id`	null \| integer	Updated dependency feature id in the same project. Use null to clear the dependency.

update_project_context WRITE Destructive

Use this to replace the project's planning context with the latest authoritative context, constraints, or operating notes.

Input schema

project_id_or_slug Required string

Project identifier. Accepts either the numeric id or the friendly slug.

context Required string

Full replacement project context text.

Example Requests

Start by listing tools, then call a tool by name with JSON arguments.

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/list"
}

{
  "jsonrpc": "2.0",
  "id": 2,
  "method": "tools/call",
  "params": {
    "name": "list_projects",
    "arguments": {}
  }
}

Notes

The tool list on this page is pulled from the registered Rails tool classes at request time.
Tool outputs are structured JSON and are also returned as text content for MCP client compatibility.
Project and feature identifiers generally accept either a numeric id or a friendly slug.