mcpbeat Sign in

Brightly MCP Server

by brightlyai Your server? Claim it
answering

Brightly is answering right now. Last checked 8 min ago.

Run your Brightly account from your AI agent: leads, conversations, appointments, sequences.

Uptime history 12 days of history
12 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
303 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Brightly every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

run in your terminal
claude mcp add brightly --transport http https://api.brightlyai.app/mcp
Settings → Connectors → Add custom connector, then paste this address
https://api.brightlyai.app/mcp
~/.codex/config.toml
[mcp_servers.brightly]
url = "https://api.brightlyai.app/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "brightly": {
      "url": "https://api.brightlyai.app/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "brightly": {
      "type": "http",
      "url": "https://api.brightlyai.app/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://api.brightlyai.app/mcp streamable-http sign-in 250 ms 8 min ago

Alternatives to Brightly

same job, measured the same way
Userport
by userport

Read and answer support conversations, and run outbound email and chat sequences, from your AI.

answering
Asyntai
by asyntai

Run your website's AI support agent: knowledge, conversations, leads and live replies.

48 installs/wk 70 tools answering
Leporis WhatsApp
by admin-rstechie

Send and read WhatsApp messages on your Leporis account from AI coding agents, via your own API key.

answering
Slack MCP Server
by stevenvo

Read Slack conversations, threads, user info, and search messages from your MCP client.

110 installs/wk local only
SNAIL
by joinsnail

Public agent conversations: read, post and reply with your SNAIL account. Humans observe.

6 tools answering
Clean
by cleanmcp

Clean finds your next customers: ICP, researched leads, replies and sequences, from any agent.

answering
JooVoice
by joovoice

Lets your AI agent make real phone calls: bookings, appointments, cancellations, refunds.

answering
Sellinger CRM
by sellinger

Manage Sellinger AI SDR CRM leads, conversations and pipeline from any MCP client.

51 installs/wk local only

Brightly — questions

Answers built from our own checks of this server.

Why is there no tool list for Brightly?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Brightly working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 303 ms. The bar chart above shows every period we have measured.
How do I connect Brightly?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Brightly?
No API key is involved. Brightly answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Brightly?
It answers our handshake in 303 ms on average, which is faster than 47% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.