Documentation

Overview

MCP-MD-Sharing is a platform for sharing and versioning Markdown documentation as a team. It works in two ways, with exactly the same permissions on both sides:

The web app (this site) — create organizations, projects, documents, manage members, and search.
An AI agent connected to the MCP server — Claude Code, Cursor, Codex, or any other Model Context Protocol–compatible tool — to read, create, edit, and search your documents directly from your editor.

An organization contains projects, and a project contains .md documents. Every save creates a new immutable version — nothing is ever overwritten.

Creating an account and signing in

From the Sign in page, you can create an account in two ways:

With an email address and a password.
By signing in directly with a Google account ("Continue with Google" button).

Once signed in, you land on your dashboard. If you're not part of any organization yet, you can create one right away.

Organizations and projects

Permissions work at two levels:

Level	Roles	What they can do
Organization	`owner`, `admin`, `member`	An organization owner or admin can manage the organization itself (rename, delete, manage members) and automatically administers every project it contains.
Project	`reader`, `editor`, `admin`	A reader can only view documents. An editor can also create and edit them. A project admin can additionally rename/delete the project and manage its members.

On the Organization page, you can create an organization, see the ones you belong to, add members, and manage each one. On the Projects page, you get the same for your projects: search, sort, add files, manage members, and delete.

Documents and versions

A document is created either by typing its content directly, or by dragging and dropping one or more .md files. Every save creates a new version — nothing is ever lost.

When you open a document, you can:

View and edit the current content, then save a new version.
Browse the full history of every past version.
Select two versions and click Compare to see a character-level diff (green = identical, red = removed, orange = modified).
Restore an old version as the new current version.

If two people edit the same document at the same time, the second save is rejected with a conflict message — just reload to pick up the latest version, then re-apply your edit.

Search

The Search page and the MCP server's search tool both use hybrid search: semantic (it understands the meaning of your question, not just exact words) and keyword-based. Results are always scoped to the projects you have access to — you'll never see a document from a project you're not a member of.

Connecting the MCP server to your AI tools

This is what lets an agent like Claude Code, Cursor, or Codex read and edit your documents directly from your editor, with the same permissions as the web app.

Step 1 — Create an API key

Go to the Settings & API Keys page.
Give your key a name (e.g. your computer's name) and click Create key.
Copy the key right away — it will never be shown in full again (only a fingerprint is kept in the database, like a password).

Step 2 — Connect your tool

Every MCP-compatible tool needs the same two things: the server address and your API key as an authorization header.

Server address: https://mcp-md-sharing.tkissdev.com/api/mcp
Authorization header: Authorization: Bearer <your-api-key>

Claude Code — in a terminal, run:

claude mcp add --transport http mcp-md-sharing https://mcp-md-sharing.tkissdev.com/api/mcp --header "Authorization: Bearer <your-api-key>"

Cursor — add this to Cursor's MCP config file (~/.cursor/mcp.json, or .cursor/mcp.json at your project root):

{
  "mcpServers": {
    "mcp-md-sharing": {
      "url": "https://mcp-md-sharing.tkissdev.com/api/mcp",
      "headers": {
        "Authorization": "Bearer <your-api-key>"
      }
    }
  }
}

Codex, or any other MCP-compatible tool — the exact configuration syntax varies by tool and changes over time. Check that tool's own MCP documentation for how to add a remote (HTTP) MCP server, and give it the server address and authorization header above.

Step 3 — Test that it works

Once connected, just ask your agent something like "List my MCP-MD-Sharing projects" or "Search my documents for 'authentication'". If it replies with your actual projects or documents, the connection works. If you get an authorization error, check that the key hasn't been revoked on the Settings & API Keys page.

Tools available to AI agents

Tool	Description
`list_projects`	List the projects you can access
`list_documents`	List the documents in a project
`read_document`	Read the current version of a document
`create_document`	Create a new document
`update_document`	Save a new version of a document
`get_history`	List a document's version history
`get_version`	Read a specific version of a document
`restore_version`	Restore an old version as the current version
`search`	Hybrid semantic + keyword search

Troubleshooting

"Unauthorized" when connecting your agent — the API key is invalid or has been revoked. Create a new one from Settings & API Keys.
The agent finds no projects — make sure you're a member of at least one organization or project with the same account used to create the API key.
"Version conflict" when saving a document — someone else (or your agent, in another tab) already saved a newer version. Reload the page or re-read the document to get the latest version before re-applying your edit.