// MCP TOOL REFERENCE

OPENSPEC TOOLS

11 tools from the Openspec MCP Server, categorised by risk level.

READ TOOLS

openspec_init Initialize OpenSpec in your project openspec_instructions Output enriched instructions for an artifact or apply openspec_list List items (changes or specs). Returns a JSON array when --json is used. openspec_read_file Read any OpenSpec artifact directly. Much faster than show — use this when you need file contents. openspec_refresh_cache Force refresh the cached directory listing. Use if you suspect changes were made outside OpenSpec tools. openspec_show Show a change or spec. Use type to specify if it is ambiguous. openspec_status Display artifact completion status for a change openspec_validate Validate a change proposal or spec

WRITE TOOLS

openspec_archive Archive a completed change and update main specs 2/5 openspec_update Update OpenSpec instruction files 2/5

EXECUTE TOOLS

openspec_new_change Create a new change directory 3/5

// FAQ

How many tools does the Openspec MCP server have? +

The Openspec MCP server exposes 11 tools across 3 categories: Read, Write, Execute.

How do I enforce policies on Openspec tools? +

Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the Openspec server.

What risk categories do Openspec tools fall into? +

Openspec tools are categorised as Read (8), Write (2), Execute (1). Each category has a recommended default policy.

Enforce policies on Openspec

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept

github.com/policylayer/intercept →