Relentless

Relentless MCP Server provides a robust bridge between your Relentless API and Notion databases, allowing an AI assistant to read from and write to your Notion data with built-in validation, retries, and clear error handling. It runs locally and authenticates with your Relentless API key to keep actions secure and reliable.

How to use

You use the Relentless MCP Server by configuring a client (an MCP-enabled AI like Claude) to connect to the locally running MCP server and then issuing high-level actions such as listing your databases, inserting new Notion entries, or reading existing data. The server automatically validates data against your Relentless schema before any insert, retries on transient failures, and provides clear error messages with actionable fixes. Your API key remains the single trusted credential, and all requests respect a 30-second timeout to prevent hanging.

How to install

pnpm install
pnpm build

Configure your Claude Desktop client to start the MCP server locally. Use the following config snippet exactly as shown:

{
  "mcpServers": {
    "relentless": {
      "command": "node",
      "args": [
        "/absolute/path/to/relentless-cms-ts/packages/relentless-mcp/build/index.js"
      ],
      "env": {
        "RELENTLESS_API_KEY": "rts_your_api_key_here"
      }
    }
  }
}

Important: Replace the path with the actual absolute path to this package and replace rts_your_api_key_here with your Relentless API key. This config uses a single environment variable and enables automatic validation against the Relentless schema.

## Configuration and start flow

1) Build the MCP server locally with your package manager. 2) Create a Claude Desktop configuration that points to the built index. 3) Restart Claude Desktop and verify the MCP server appears under the MCP connections panel. The server will fetch schemas from the Relentless API automatically and perform validation before insertions.

## Security and reliability

- Your Relentless API key is stored only in your Claude Desktop configuration and is never exposed in the MCP server logs. - The MCP server runs on your machine, and all requests are routed through the Relentless API for authentication and access control. - Validation checks ensure required fields, data types, and allowed options before any Notion write operation. - Automatic retries with exponential backoff handle transient failures, and a 30-second timeout protects against hanging requests.

## Troubleshooting

If the MCP server does not appear in Claude Desktop after configuration, confirm the absolute path in the config is correct, ensure you have built the project, and restart Claude Desktop. Check logs for errors and verify your Relentless API key is valid and active.

## Notes on usage and features

Key features include pre-insert validation, type checking against Notion schema, required field detection, size limits, automatic retries, rate limit handling, timeout protection, and improved error messages with specific fix suggestions. Use the listed tools to interact with your Notion databases: relentlessly list databases, insert validated entries, read entries, and generate indices for quick discovery.

## Developer and build details

Dev workflow uses pnpm for install and build. The MCP server runs locally and relies on the Relentless API for schema fetching and Notion integration. See the commands above for a complete setup flow.

## Available tools

### relentless\_list\_databases

Lists all Notion databases connected to your Relentless account, used to discover available databases before other actions.

### relentless\_insert

Creates a new Notion database entry with automatic validation for required fields, data types, and allowed options.

### relentless\_read

Reads a specific Notion entry by slug from a chosen database.

### relentless\_list

Lists all entries from a database with full content.

### relentless\_index

Retrieves an index of entries (slugs and titles only) for fast browsing.