Likerts

Name: Likerts
Author: crosstabs

by crosstabsversion 0.1.1i★ –iComputer or cloud

Registry nameio.github.crosstabs/likerts

Install

Overview

Description from the maker (original English)

Manage open-source in-product surveys, collections, responses and exports with scoped access.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Computer or cloud
Transport: stdio, Streamable HTTP
Category: Docs, sheets & office work
You need to fill in: LIKERTS_API_URL, LIKERTS_TOKEN, LIKERTS_COLLECTION_TOKEN, Authorization

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on the maker’s server: what you ask it goes through their server.
You fill in yourself: LIKERTS_API_URL, LIKERTS_TOKEN, LIKERTS_COLLECTION_TOKEN, Authorization

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

Runs in the cloudNothing to install; it connects over the internet
npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Or run it on your computer

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "likerts": {
      "command": "npx",
      "args": [
        "-y",
        "@likerts/mcp"
      ],
      "env": {
        "LIKERTS_API_URL": "your-value",
        "LIKERTS_TOKEN": "your-value",
        "LIKERTS_COLLECTION_TOKEN": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add --transport http likerts 'https://likerts-mcp.onrender.com/mcp/{workspaceId}' --header 'Authorization: your-value'

Or run it on your computer

claude mcp add likerts --env LIKERTS_API_URL=your-value --env LIKERTS_TOKEN=your-value --env LIKERTS_COLLECTION_TOKEN=your-value -- npx -y @likerts/mcp

Fill in the empty values before running it.

The address contains {…} parts that only you know (such as your account), so copy it and fill them in.

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "likerts": {
      "url": "https://likerts-mcp.onrender.com/mcp/{workspaceId}",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

Or run it on your computer

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "likerts": {
      "command": "npx",
      "args": [
        "-y",
        "@likerts/mcp"
      ],
      "env": {
        "LIKERTS_API_URL": "your-value",
        "LIKERTS_TOKEN": "your-value",
        "LIKERTS_COLLECTION_TOKEN": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

The address contains {…} parts that only you know (such as your account), so copy it and fill them in.

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "likerts": {
      "type": "http",
      "url": "https://likerts-mcp.onrender.com/mcp/{workspaceId}",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

Or run it on your computer

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "likerts": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@likerts/mcp"
      ],
      "env": {
        "LIKERTS_API_URL": "your-value",
        "LIKERTS_TOKEN": "your-value",
        "LIKERTS_COLLECTION_TOKEN": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

LIKERTS_API_URL required env
Your Likerts API origin. Requires HTTPS outside exact loopback development hosts.
LIKERTS_TOKEN secret required env
Workspace-bound service credential with only the scopes needed by this agent.
LIKERTS_COLLECTION_TOKEN secret env
Optional collection credential for collection configuration and response submission only.
Authorization secret required HTTP header
Bearer followed by your workspace's scoped service credential.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account crosstabs, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
The address needs your own account values, so we cannot check it for you
– Not applicable
Sign-in with OAuth
The address needs your own account values, so we cannot check it for you
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Compared with others in Docs, sheets & office worki

More stars than 0% of the other 3541 servers in this category
Published to the registry more recently than 37% of the other 3541 servers in this category
Basic checks equal to or better than 100% of the other 3541 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Likerts safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: LIKERTS_API_URL, LIKERTS_TOKEN, LIKERTS_COLLECTION_TOKEN, Authorization

Does it run on my computer or in the cloud?

Either way works: install it on your computer or connect to the cloud version.

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.1) reached the registry 2 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Agent-Native Calendar, Excel MCP Server, MCP Server for Excel

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Agent-Native Calendar

by BuilderIO

Agent-Native Google Calendar - manage events, sync, and public booking

Runs in the cloud★ 7,620MITUpdated 2 months ago

Install

Excel MCP Server

by haris-musa

Lets AI create and edit Excel files itself, including formulas, charts and PivotTables, without Excel installed.

Runs on your computer★ 4,276MITUpdated 7 days ago

Install

MCP Server for Excel

by sbroenne

Excel automation for AI - Sheets, Power Query, DAX, VBA, Tables, Ranges and more. Windows only.

Runs on your computer★ 847MITUpdated 4 days ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Likerts MCP server

Operate the free, MIT-licensed Likerts survey platform from an MCP client. The server exposes the same typed operations and authorization boundaries as the HTTP API and CLI.

The hosted server is listed in the official MCP registry as io.github.crosstabs/likerts. Configure your workspace ID and scoped service credential in your MCP client. The listing does not make workspace data public.

Install

Install a published version from npm:

npm install --global @likerts/mcp@0.1.0

Alternatively, download the MCP tarball from the community release and run npm install --global /absolute/path/to/the-mcp-package.tgz. Node.js 22 or newer is required.

Configure your MCP client to run likerts-mcp over stdio. Set LIKERTS_API_URL to your API origin and supply a scoped LIKERTS_TOKEN through your environment or secret manager. The local API defaults to http://127.0.0.1:8080. Collection operations use LIKERTS_COLLECTION_TOKEN separately; keep management credentials out of embedded apps and tool arguments.

Copy the local Codex configuration or local Claude Code configuration. Both read the service credential from your environment; start with only the scopes your workflow needs.

For a source checkout:

npm ci --prefix tools/mcp

npm run build --prefix tools/mcp node tools/mcp/dist/main.js

Launch the command from an MCP client; stdout is reserved for protocol messages. Authentication and permission checks remain enforced by your API.

Remote connection

The optional hosted endpoint is https://likerts-mcp.onrender.com/mcp/{workspaceId}. It requires the workspace's scoped service credential. It is a hosted reference preview for synthetic, non-sensitive evaluation data, with the same operational and support limits as the web preview. Self-hosters use their own remote host.

Setup for Codex and Claude · Quickstart · API reference

Registry metadata and release verification

server.json matches published registry listing 0.1.1, adding npm package @likerts/mcp@0.1.0 alongside the remote endpoint. The publication workflow passed on 13 September 2026 at source fe7588fabf2ee596a963ed943764021084f7d49e; independent readback matched both npm and remote metadata. Listing and npm package versions are independent. Registry 0.1.0 and the npm tarball remain immutable.

From a source checkout with Docker, Rust stable and Node 22+, run:

npm ci --prefix tools/mcp

node scripts/check-mcp-registry.mjs bash -c 'source scripts/dev-env.sh; node scripts/check-mcp-lifecycle.mjs'

The registry check validates the official pinned schema, exact npm package identity and version, and published mcpName. The lifecycle check installs the public npm artifact in a temporary consumer, starts the real Rust API on loopback with disposable PostgreSQL and a restricted runtime role, discovers every tool, and uses a scoped service credential to create/publish a survey, create a collection, submit/retry/read/delete a response and close collection access. It also proves insufficient-scope denial and credential revocation. It deletes its temporary workspace/files. This does not test a specific Codex/Claude UI, backup/restore behavior or the hosted service.

Maintainers publish metadata from an exact main commit only after both required jobs in its Verify foundations push run succeed:

gh workflow run publish-mcp.yml --ref main \

-f source_sha=FULL_TESTED_MAIN_COMMIT \ -f registry_version=NEW_UNPUBLISHED_REGISTRY_VERSION

The workflow requires that SHA to match its dispatch commit, rejects an existing registry version, repeats schema/npm/lifecycle checks, checks remote health/authentication denial, publishes through GitHub OIDC, and verifies the resulting record. It does not publish npm or rebuild the historical community release. If publication succeeds but final verification fails, inspect that exact registry version before retrying; existing records are never overwritten.

For an opt-in check through installed, already authenticated Codex and Claude Code CLIs, add --clients to the lifecycle command. This preflights account state and makes one bounded model request per authenticated client using only surveys_list and a temporary surveys:read credential for an empty local workspace. It does not purchase access, alter global client configuration, or run in ordinary CI. Each client has a three-minute timeout; unavailable authentication or approval is reported separately from the account-free protocol test. The optional run exits nonzero unless every selected client returns a verified empty tool result; use --clients=claude to retry only Claude after authentication. Client output is summarized without publishing raw logs or credentials.

On 13 September 2026, Codex CLI 0.154.0 completed a verified surveys_list call through public @likerts/mcp@0.1.0 against a temporary scoped PostgreSQL workspace. Claude Code 2.1.201 parsed the configuration but remains unauthenticated, so its real-client call is still pending. See exact client evidence and the owner login action. The earlier Codex failure was traced to the test harness leaving stdin open; immediate EOF and reliable timeout tracking now have regression tests.

Likerts

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Or run it on your computer

Or run it on your computer

Or run it on your computer

Or run it on your computer

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Docs, sheets & office worki

Common questions

Alternatives

Agent-Native Calendar

Excel MCP Server

MCP Server for Excel

README from the maker

Likerts MCP server

Install

Remote connection

Registry metadata and release verification