Codegworkspace MCP

What codegworkspace-mcp does

The codegworkspace-mcp MCP server provides a shared workspace for tracking and handing off coding-agent sessions in CodeG. Its tools cover four workflow steps: registering an agent session, viewing the current workspace roster, writing a handoff note, and exporting a summary of a session.

The hosted service is designed for workflows that need more than an agent's local conversation history. It exposes receipt-oriented JSON, usage logs, and audit-related session data through MCP tool calls. The repository itself is not the production implementation; it contains public documentation and reference information for the hosted service.

How it works

The service is reached through a remote Streamable HTTP MCP endpoint at https://codegworkspace.clauxel.com/mcp. An MCP client sends JSON-RPC requests to that endpoint, and production requests must include a bearer token in the Authorization header:

Authorization: Bearer <token>

The token is issued through the product website after selecting a plan and creating or requesting access. Browser requests to the MCP path without authentication return a JSON error rather than exposing internal service details. Public metadata is available through the service's server-card endpoint.

The codegworkspace-mcp MCP server fits teams or agent workflows where several coding sessions need to be visible in one workspace, where one agent must leave context for another, or where session activity needs exportable records.

Setup and configuration

1. Open the CodeG Agent Workspace website and select a plan.
2. Create or request an API token.
3. Configure an MCP client that supports remote Streamable HTTP servers with the MCP endpoint.
4. Send JSON-RPC tool requests with the bearer token.

The documented MCP endpoint is https://codegworkspace.clauxel.com/mcp. The public server card is available at https://codegworkspace.clauxel.com/server-card.json. No local installation or source build is described, because the repository documents a hosted service rather than containing its private production code.

Tools and capabilities

The available MCP tools are:

• register_agent_session for adding an agent session to the workspace.
• read_workspace_roster for reading the sessions or agents currently represented in the workspace.
• write_handoff_note for recording information intended for a later agent or workflow step.
• export_session_summary for producing a session summary in the service's receipt-oriented JSON format.

The service also advertises usage logs and audit-ready JSON around its hosted tool calls. The provided material does not specify individual tool arguments, response schemas, retention rules, or export fields.

Limitations and notes

Access is paid and production calls require a bearer token. The supplied documentation does not identify specific MCP client products, provide local or self-hosted deployment instructions, or describe a development mode. It also does not state whether the service supports transports other than Streamable HTTP.

The repository should therefore be treated as a documentation and directory-submission reference. Developers evaluating the codegworkspace-mcp MCP server should verify plan pricing, token issuance, client compatibility, and the exact tool schemas from the hosted service before implementation.