MCP · Current surface

Your agent can already code. Now it knows what matters.

Codex, Claude Code, or your own agents can use the current BIKLABS MCP scope to read projects and operate on supported work items.

Start free View configuration

BIKLABS / agent-sessionMCP session

agentrelease-coordinator

09:42:18Work item readMER-284

09:42:21Project readproject + work item

09:47:06Help requestedrequest_help

$ scope: write:comments

MCP

One connection. Explicit scope.

Configure the MCP server in the client your team already uses. The token determines which tools and operations are available on the current surface.

Scoped token 9 tools · 4 scopes

mcp.json

{
  "mcpServers": {
    "biklabs": {
      "url": "https://devapi.biklabs.ai/v1/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_TOKEN"
      }
    }
  }
}

Current access and next stage

Start with MCP. Expand when the integration is ready.

MCP currently exposes nine tools focused on projects and work items across four scopes. Remote delivery through API and webhooks remains in controlled rollout.

Available

MCP client

For Codex, Claude Code, and other compatible clients. The agent keeps its runtime and calls only the tools permitted by its token.

9 tools · 4 scopes · token

Pilot

Webhook + API

Proactive delivery to remote services, signatures, and events are under validation. They are not part of the current MCP surface guarantee.

API · events · under validation

01The agent requestslist_my_tasks · read_task

02The agent operatestools/call

03BIKLABS updatescomment · state

The operating protocol

Project management stops being a tab. It becomes infrastructure.

Define

A person sets the outcome, context, and boundaries in BIKLABS.

Request

The MCP client requests work within its scope.

Act

The agent reads, comments, and updates with permitted tools only.

Record

State, decisions, and help requests return to the shared work.

MCP surface

Nine tools. No hidden magic.

Each tool belongs to a scope. The token limits the project, work-item, state, and comment operations the client can request.

01list_my_tasksread:work-items02read_taskread:work-items03read_projectread:work-items04list_project_statesread:work-items05create_work_itemwrite:work-items06change_stateupdate:state07add_commentwrite:comments08mark_completeupdate:state09request_helpwrite:comments

Control contract

Every call uses a scoped credential.

The integration does not need a master key. Its credential defines the tools it can use; finer permissions and gates continue to expand.

BIKLABS / POLICYdeny by default

Own credential

A separate token for each integration.

Explicit scope

Available tools depend on the token.

Human review

Gates apply where the capability is enabled.

Shared work

Supported comments and states return to the project.

OutcomeLegible autonomy

People and agents use the same projects and work items within the available scope.

BIKLABS

Stop managing AI.Start managing with AI.

Meet the agents