Relentless MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RELENTLESS_API_KEY | Yes | Your Relentless API key for authentication |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| relentless_list_databasesA | List all Notion databases connected to your Relentless account. Use this first to discover available databases, then use other tools to read/write data. Returns database names that can be used with other tools. |
| relentless_insertA | Insert a new entry into a Notion database via Relentless API. Data is automatically validated before insertion to catch errors early. Use this to create new documentation, blog posts, leads, or any structured data. The data will be immediately visible in Notion and accessible via the Relentless API. |
| relentless_readA | Read a specific entry from a Notion database by its slug. Returns the full entry with all properties and content. |
| relentless_listB | List all entries from a Notion database. Returns full content for all entries. Use this to see what content exists or to search through entries. |
| relentless_indexA | Get an index of all entries (slugs and titles only). This is faster than relentless_list when you only need to see what entries exist without their full content. Useful for navigation or sitemap generation. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: relentless_index provides slugs/titles only, relentless_insert creates new entries, relentless_list returns full content of all entries, relentless_list_databases lists available databases, and relentless_read retrieves a specific entry by slug. There is no overlap in functionality that would cause confusion.
All tools follow a consistent 'relentless_verb' naming pattern (e.g., relentless_index, relentless_insert, relentless_list, relentless_list_databases, relentless_read). This uniformity makes the tool set predictable and easy to navigate.
With 5 tools, the server is well-scoped for its purpose of interacting with Notion databases via the Relentless API. Each tool serves a specific role (discovery, reading, writing), and there are no extraneous or missing tools for the core operations.
The tool set covers essential CRUD operations for Notion databases: create (relentless_insert), read (relentless_read, relentless_list, relentless_index), and discovery (relentless_list_databases). However, it lacks update and delete tools, which are minor gaps that agents might need to work around for full lifecycle management.