Copilot MCP Server

by ohaiibuzzle

Overview Schema Source Related Servers Discussions Admin

Python

Local

copilot_prompt

Run a Copilot prompt non-interactively and retrieve its stdout, stderr, and exit code.

Instructions

Run a non-interactive Copilot prompt (copilot -p ...) and return stdout/stderr/exit code.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "prompt": "<prompt>"
    },
    "name": "copilot_prompt"
  }
}

Input Schema

Name	Required	Default
`cwd`	No
`model`	No
`prompt`	Yes
`allow_all`	No
`extra_args`	No
`output_format`	No	text
`timeout_seconds`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 7, 2026

TDQS

A3.5/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden. It discloses that execution is non-interactive and that stdout/stderr/exit code are captured and returned. However, it does not mention potential side effects, prerequisites like authentication, or that the prompt may trigger external service calls. This is a moderate level of transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence with no wasted words. It clearly states the action and the return value, making it easy to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having an output schema, the description is too thin for a tool with 7 parameters and a sibling tool. It omits any information about when to use this over `copilot_command`, does not explain non-obvious parameters like `allow_all` or `extra_args`, and lacks any caveats about timeout or output format. The completeness is low.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate for unannotated parameters. It only implicitly covers the 'prompt' parameter by mentioning the `copilot -p` command; no explanation is given for cwd, model, allow_all, extra_args, output_format, or timeout_seconds. This is insufficient for a 7-parameter tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool runs a non-interactive Copilot prompt via `copilot -p` and returns stdout/stderr/exit code. It identifies the specific verb ('run'), resource ('Copilot prompt'), and distinguishes itself from the sibling tool by emphasizing 'non-interactive'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context by specifying 'non-interactive', which suggests using this tool when you want a one-shot prompt rather than an interactive session. However, it does not explicitly mention the sibling tool `copilot_command` or provide when-not-to-use guidance, so the usage guidance is only implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server