Your MCP servers and skills, inside every task run you choose.

An extension profile bundles the MCP servers and skills an agent should have: your issue tracker, your internal docs, your team's review checklist. Pick a profile on New Task or an automation, and the run starts with exactly that set.

An agent extension profile: the runbooks MCP server over HTTPS with two read-only tools and a write-only bearer token, plus the incident-runbooks skill pinned to a commit with its SHA-256 digest
A profile with a runbooks MCP server, two allowed tools, and a skill pinned to a commit.

Feature overview

MCP servers, tool by tool

Add a remote HTTPS MCP server, discover its tools, and tick the ones the agent may call. The agent sees only those.

Skills, pinned to a commit

Import a skill from a GitHub repository or an archive. ProPR pins the exact commit and mounts the skill read-only in the task container.

Versioned profiles

Every save creates a new revision, so you always know which tools and skills a run had.

The agent gets the tools. ProPR keeps the credentials.

ProPR stores each server's token encrypted on your instance and never sends it to the task container. Write access is a separate opt-in on New Task, and the task timeline records every tool call.

  • Claude Code and Codex task runs take profiles. Goals run without them.
  • Limit a profile to specific agents and repositories.
  • Administrators manage profiles in Settings → Agent Extensions & Packages. The agent extensions guide covers imports, the operator catalog and backups.