Productivity · Remote MCP server
Writbase
MCP-native task management for AI agent fleets with scoped permissions and provenance.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.Writbase/writbase- Version
- 0.1.3
- Status
- Active
- Category
- productivity
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-03-15
- Updated
- 2026-03-15
- Publisher
- Writbase (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/Writbase) · how
- Repository
- github.com/Writbase/writbase
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://{PROJECT_REF}.supabase.co/functions/v1/mcp-server/mcp | Authorization |
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.
- Checked
- Not requested: URL template placeholder
- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npmruntime: npx | writbase | 0.1.3 | stdio |
How to connect Writbase
Writbase is a remote MCP server: there is nothing to install. Its endpoint is https://{PROJECT_REF}.supabase.co/functions/v1/mcp-server/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 URL contains placeholders to fill in before connecting: {PROJECT_REF}.
The registry entry declares an HTTP header for the connection: Authorization. Clients that accept custom headers set it with the server's URL.
It can also run locally from a Node.js package published to the npm registry: writbase version 0.1.3. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y writbase@0.1.3. It reads these environment variables: WRITBASE_URL (required) and WRITBASE_AGENT_KEY (required, secret); set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"writbase": {
"command": "npx",
"args": [
"-y",
"writbase@0.1.3"
],
"env": {
"WRITBASE_URL": "<value>",
"WRITBASE_AGENT_KEY": "<secret>"
}
}
}
}Derived from the registry entry, not tested here. 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 productivity servers
| Server | Runs |
|---|---|
| WorkoraiWorkorAI talent marketplace MCP: candidate job search and employer hiring with explainable matching. | Remote · HTTPLive check: ✓ handshake |
| WorkspaceFloreal Holidays Belgium: live prices and availability; staff run M&E dossiers, day sheets, tasks. | Remote · HTTPLive check: ✓ handshake |
| WorkWingField service management: find customers, read the schedule, create and book jobs, add notes. | Remote · HTTPLive check: sign-in required |
| WrikeManage projects, tasks, and workflows with Wrike project management. | Remote · HTTP, SSELive check: ✗ no handshake |
| Writing MCPMetadata-first fiction editing and reasoning tools for long-form writing projects. | Local · stdio |
| WritioLinkedIn-native AI content creation, scheduling & analytics via MCP. | Local · stdio |
| WufooRead forms, fields, entries, reports and comments by field title, and submit entries. | Remote · HTTPLive check: ✓ handshake |
| www.bounceprotect.comEmail validation and SMTP verification for Claude Desktop, Cursor, and Claude Code. | Local · stdio |