Business operationsPublic source

Project MCP Server

A fully-featured project-management layer for ADK-Rust Enterprise agents. 27 MCP tools covering projects, work items, sprints, milestones, dependencies, time tracking, and reporting — the building blocks for planning,…

Open the source Read the official guide ↗

What it gives an agent

A purpose-built capability behind one MCP connection.

The server owns its domain logic and publishes a tool contract an MCP client can discover. ADK-Rust can load that contract into an agent, normalize each schema for the chosen model provider, and keep the connection lifecycle outside the agent’s business logic.

Provides project capabilities through a typed MCP contract.

Architecture

How Project MCP Server fits into an agent system.

The model never needs the implementation details or credentials of the system behind the server. It sees reviewed tool definitions. The MCP client handles discovery and calls, while the server keeps ownership of validation, policy, and communication with its domain system.

ADK-Rust agent

Chooses a capability from the reviewed tool catalog.

→

MCP client

Discovers schemas, sends calls, and receives typed content.

→

Project MCP Server

Validates the request and owns 27 documented tool contracts.

→

Domain system

Keeps the API, data, credentials, and business rules behind the server.

Connection: stdio · Server framework: ADK MCP SDK + rmcp

Project MCP Server architecture diagram from its official repository

Tool catalog

What can an agent ask Project MCP Server to do?

Each tool has a stable name, a human-readable purpose, and a JSON input contract discovered during MCP initialization. Risk classes come from the project’s registry manifest when one is available.

27 named tools

create_project

Create a project with a KEY, name, lead, and members

internal write

get_project

Get a project's details

read only

list_projects

List projects, optionally by status

read only

set_project_status

Change a project's status

internal write

add_member

Add a member to a project

internal write

create_task

Create a work item (epic/story/task/bug/subtask)

internal write

get_task

Get a task's full detail

read only

search_tasks

Search tasks by project, text, status, assignee, type, sprint, or label

read only

update_task

Update task fields

internal write

transition_task

Transition a task through its workflow (enforces valid transitions and dependency blocks)

internal write

assign_task

Assign or unassign a task

internal write

set_labels

Set a task's labels

internal write

Governance

Understand the effect of every tool.

A server connection inherits the authority of its credentials and deployment environment. The declarations below come from this project’s README and MCP registry manifest; your application still decides which tools an agent receives and where approval is required.

17 internal write10 read only

Gated writes — status changes (set_project_status, transition_task, set_sprint_status, set_milestone_status) require approval in production; reads/reports are read_only.
Validated workflow — invalid transitions and dependency cycles are rejected.
Integration scaffold — the in-memory store is for development; back it with a durable store and bind actors to authenticated identities in production.

MCP surface

What the current documentation declares.

MCP can carry tools, resources, prompts, structured results, progress, cancellation, and long-running work. This record highlights the modern protocol features explicitly mentioned by this repository.

Completion

Long-running tasks

ADK MCP SDKrmcpRegistry manifest

Install and connect

Follow the project’s documented starting point.

Install the server in the environment that owns its credentials and domain access. Add it to your MCP host, verify the discovered tools, and narrow the toolset before giving it to a production agent.

Install

cargo install mcp-project

ADK-Rust connection shape

let toolset = McpToolset::from_stdio(
    "mcp-project",
    ["mcp-project"],
).await?;

let agent = LlmAgentBuilder::new("agent")
    .tools(toolset.tools().await?)
    .build()?;

Commands and configuration are extracted from the public README. Confirm prerequisites, environment variables, and release-specific options in the official documentation before deployment.

Official documentation

Continue with the project maintainers’ source of truth.

This page provides an approachable map of the server. The repository remains authoritative for exact schemas, prerequisites, configuration, examples, tests, releases, and security updates.

Overview ↗README.md CHANGELOG ↗CHANGELOG.md Architecture ↗docs/architecture.svg Issues and support ↗github.com issues

Keep exploring