Developer · Remote MCP server
Moxt Workspace
Browse and manage files in your Moxt AI workspace from any MCP client.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
ai.moxt/mcp-workspace- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-05-13
- Updated
- 2026-05-13
- Publisher
- ai.moxt
- Namespace
- Namespace verified by the MCP Registry via the domain moxt.ai · how
- Website
- moxt.ai
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.moxt.ai/openapi/v1/mcp | Authorization (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401
- Checked on
- 2026-10-05
How to connect Moxt Workspace
Moxt Workspace is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.moxt.ai/openapi/v1/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Mova Flat RunnerGoverned AI workflows with human approval gates and audit trails for Claude and MCP clients. | Local · stdio |
| MOVA MCP ConnectorThin MOVA MCP proxy for bindings, transport resolution, and upstream tools/call execution. | Local · HTTP |
| MowgliProduct canvas: iterate on your product's design with your coding agent, synced to code. | Remote · HTTPLive check: sign-in required |
| Moxie DocsLiving docs and MCP context for GitHub repos - conventions, gaps, and source-cited pages on merge. | Remote · HTTPLive check: ✓ handshake |
| MozaikaMeasured design systems decoded from 588 real products, for coding agents. | Remote · HTTPLive check: ✓ handshake |
| Mozilla ObservatoryMDN HTTP Observatory - grade any website's HTTP security headers and get the specific fixes, from… | Remote · HTTPLive check: ✓ handshake |
| MPM-CodingTool-first MCP: AST nav, impact/flow, task chains, memo/recall. | Local · stdio |
| mq-bridge-appMove data between 15+ databases, queues and files at high throughput, without it entering context. | Local · stdio |