Codex Peer
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| peer_healthA | Connect to a peer Codex app-server and run initialize. |
| peer_messageC | Send a natural-language message to a peer Codex thread. |
| peer_waitA | Check a previously-started peer turn without treating long work as failure. |
| peer_wait_until_completeA | Quietly wait for a previously-started peer turn and return only when it completes or the wait window ends. |
| peer_threadsC | List peer Codex threads. |
| peer_readB | Read a peer Codex thread and summarize its recent turns. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/shotaro311/codex-peer'
If you have feedback or need assistance with the MCP directory API, please join our Discord server