Consentease

io.consenteasePublished by consentease.ioOfficial publisherv1.4.1Updated Oct 25, 2026

Manage ConsentEase consent banners and cookie inventories from your coding agent.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

ConsentEase MCP server lets an assistant manage consent banners and cookie inventories in a ConsentEase account from a coding agent.

What you can do
Manage consent banners and cookie inventories in a ConsentEase account from the assistant, per the registry description. The manifest lists no individual tools, so the exact operations are not documented here. It can run as a remote endpoint or as a local npm package over stdio.
When to use it
Useful when you already work with ConsentEase and want an assistant to handle consent banner and cookie inventory tasks alongside your code, instead of switching to the dashboard.
Requirements
A ConsentEase account and an API key (ce_live_…), created in the dashboard under Settings → API Keys. The key is supplied through the CONSENTEASE_API_KEY environment variable or the X-API-Key header. The remote endpoint is at consentease.io; the local option is the npm package @consentease/mcp-server over stdio. An optional CONSENTEASE_API_URL variable targets a non-production server.
Before you install
The API key is a live credential that grants access to your ConsentEase account; keep it out of shared configs and logs. The server can change consent banners and cookie inventories, so review any write actions before approving them. No tool list is published, so confirm what it can modify before installing.

Installation

In SourceWeft

  1. Open Consentease in the dashboard and add it to a workspace.
  2. Connect X-API-Key credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.consentease%2Fmcp-server/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "consentease": {
      "type": "http",
      "url": "https://consentease.io/mcp",
      "headers": {
        "X-API-Key": "<YOUR_API_KEY>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.4.1LatestOct 14, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.