Docsalot home pagelight logo
  1. Authoring MCP
  2. Authoring MCP

Use Authoring MCP to work on your Docsalot documentation from Claude, Codex, or another MCP client. Ask your assistant to read pages, save edits as drafts, publish a version, or investigate reader questions.

Your connection uses your Docsalot account’s documentation access and the permissions you approve.

​
Connect

Add this URL as a remote HTTP MCP server in your client:

https://docsalot.dev/dashboard-mcp

Name the connection authoring-mcp. Existing connections named docsalot-dashboard still work.

​
Claude.ai and Claude Desktop

1

Open Connectors

In Claude.ai, open Settings → Connectors. In Claude Desktop, open Customize → Connectors.

2

Add Authoring MCP

Add a custom connector named authoring-mcp with this URL:

https://docsalot.dev/dashboard-mcp
3

Sign in

Click Connect, sign in to Docsalot, and approve the permissions you need.

​
Cursor

1

Open your MCP configuration

Open or create ~/.cursor/mcp.json for all projects, or .cursor/mcp.json in your project for that project only.

2

Add the server

Add authoring-mcp to your mcpServers object. Keep any existing server entries.

{
  "mcpServers": {
    "authoring-mcp": {
      "url": "https://docsalot.dev/dashboard-mcp"
    }
  }
}
3

Connect and authorize

Save the file, open Cursor’s MCP settings, and connect the server. Complete the OAuth sign-in with your Docsalot account and approve access.

4

Try it in Agent

Ask Cursor: “Use Authoring MCP to list my Docsalot documentations.”

See Cursor’s MCP documentation for configuration and authentication options.

​
Claude Code

1

Create an API token

In your Docsalot team’s Settings → API Tokens, create a token with the permissions you need.

2

Set the token

In your terminal, set:

export DOCSALOT_API_TOKEN="<YOUR_DOCSALOT_API_TOKEN>"
3

Add the server

Run:

claude mcp add authoring-mcp \
  --transport http \
  -H "Authorization: Bearer $DOCSALOT_API_TOKEN" \
  https://docsalot.dev/dashboard-mcp
4

Check the connection

Run claude mcp list, then ask Claude Code to list your Docsalot documentations.

​
Codex CLI

1

Create an API token

In your Docsalot team’s Settings → API Tokens, create a token with the permissions you need.

2

Set the token

Set the token in the terminal where you run Codex:

export DOCSALOT_API_TOKEN="<YOUR_DOCSALOT_API_TOKEN>"
3

Add the server

Run:

codex mcp add authoring-mcp \
  --url https://docsalot.dev/dashboard-mcp \
  --bearer-token-env-var DOCSALOT_API_TOKEN
4

Try the connection

Start Codex from that terminal and ask it to list your Docsalot documentations.

​
Other clients

1

Add a remote server

Name it authoring-mcp and use https://docsalot.dev/dashboard-mcp with HTTP transport.

2

Authenticate

Sign in through OAuth if your client supports it, or pass a Docsalot API token in the Authorization: Bearer <TOKEN> header.

3

Verify access

Ask your assistant to list your Docsalot documentations.

Keep API tokens private. Your connection needs docs:read to read docs, docs:write to save edits, and publish to publish. Reader Questions also requires analytics:read and an Enterprise plan.

​
Try it

Start with a read:

List my Docsalot documentations, then show the pages in "My Project" and read its home page.

Save an edit:

Update the home page of "My Project" to explain our new onboarding flow. Save a draft without publishing.

After reviewing the draft:

Publish the draft you just created for "My Project".

You can also ask what readers need:

What did readers ask about "My Project" last month? Summarize the themes and show the supporting samples.

See Reader Questions to enable analytics and explore the results.

​
Available tools

Your assistant can choose the tools from a plain-language request. Expand a tool to see what it does.

​
Troubleshooting

Still stuck? Contact faizank@docsalot.dev.