Claude Code Directive MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| claude_directive_enableB | Enable or update a global temporary Codex AGENTS directive that tells Codex to use Claude Code until a specific expiry, with context guardrails and scheduled cleanup. |
| claude_directive_statusC | Report discovered Codex homes, effective AGENTS files, current directive markers, scheduler state, context policy, and optional Claude CLI availability. |
| claude_directive_disableB | Remove the active temporary Claude Code directive block using the manifest and disable the one-time cleanup scheduler. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct function: enabling, checking status, or disabling the directive. No overlap in purposes.
All tools follow a consistent `claude_directive_` prefix with verb_noun pattern (enable, status, disable), making them easily identifiable.
Three tools is exactly right for managing a lifecycle (create/read/delete) of a single directive; compact and well-scoped.
The set covers the full lifecycle: enabling (create/update), checking status (read), and disabling (delete). No obvious gaps for the stated domain.