AI assistants (MCP) - Liveday Developers

Liveday runs a public Model Context Protocol (MCP) server. Connect it to your AI coding assistant and the assistant can read this documentation and the published OpenAPI spec while it helps you build your integration.

Endpoint

https://developers.liveday.se/api/mcp

The server uses the Streamable HTTP transport. It needs no authentication because everything it serves is already public.

Read-only documentation access

The MCP server serves documentation and API definitions only. It never calls the Liveday API, and it never sees your API key or your organization's data. The code your assistant writes still authenticates with your own API key, as described in Authentication.

Setup

Claude Code

claude mcp add --transport http liveday https://developers.liveday.se/api/mcp

Claude Desktop and claude.ai

Open Settings > Connectors, choose Add custom connector, and enter https://developers.liveday.se/api/mcp as the URL.

Cursor

Add the server to .cursor/mcp.json in your project, or to ~/.cursor/mcp.json to use it in every project:

{
  "mcpServers": {
    "liveday": { "url": "https://developers.liveday.se/api/mcp" }
  }
}

VS Code

Add the server to .vscode/mcp.json in your workspace:

{
  "servers": {
    "liveday": {
      "type": "http",
      "url": "https://developers.liveday.se/api/mcp"
    }
  }
}

Other clients

Any MCP client that supports remote servers over Streamable HTTP can connect. Point it at the endpoint URL above.

Tools

Tool	Description
`list_docs`	Lists every documentation page with its slug, title and description
`read_doc`	Returns the full markdown of one page by slug, e.g. `docs/webhooks`
`search_docs`	Full-text search across the documentation, with context snippets
`list_api_endpoints`	Lists the endpoints in the OpenAPI spec, optionally filtered by keyword
`get_api_endpoint`	Returns one endpoint's full definition (parameters, request body, responses) with every referenced schema included

The tools always serve the current documentation and the current published OpenAPI spec, so you don't need to update anything when the docs change.

Example prompts

Once the server is connected, ask your assistant things like:

"Using the Liveday docs, write a function that fetches all transactions from the last 7 days, handling pagination."
"Which fields does a transaction in the Liveday API response contain?"
"How do I verify Liveday webhook signatures?"

Testing the connection

To check the server from the command line, list its tools:

curl -X POST "https://developers.liveday.se/api/mcp" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'