Take Blip

@codespar/mcp-take-blip · v0.2.2

🇧🇷 BrazilMessagingAuth · API Keylive18 tools2 env vars

Conversational platform: chatbot flows, contact management, broadcasts, and analytics. Your agent orchestrates customer journeys across channels.

Get started · free View docs

MIT · runs locally with your own credentials

Limitations

The package manifest does not declare 2 of the 2 variables the code reads.
The package manifest declares TAKE_BLIP_API_KEY, which the code does not read.

DetailsSource on GitHub

Package: @codespar/mcp-take-blip
Version: 0.2.2
npm dist-tag: latest
Category: Messaging
Auth: API Key
Country: 🇧🇷 Brazil
License: MIT
Transport: stdio · streamable-http

npm GitHub Server catalog docs

Quickstart

Install, set the credentials, make the first call.

Pick your client. The server runs locally over stdio, with your own credentials.

Add the server to your clientOne config entry. No build step, no SDK required.

Set the environment variables2 variables read by this server's code, listed below.

Restart and make the first callThe agent can call any of the 18 tools. Try send_message first.

Hosted MCP Build your own server

terminal

# Claude Code
claude mcp add take-blip -e TAKE_BLIP_ACCESS_KEY=… -e TAKE_BLIP_BOT_ID=… -- npx -y @codespar/mcp-take-blip@0.2.2
# then: /mcp to confirm the server is connected

Environment variables2 variables

TAKE_BLIP_ACCESS_KEYRead by the code; the package manifest does not declare it.

TAKE_BLIP_BOT_IDRead by the code; the package manifest does not declare it.

Names read from the package code (@codespar/mcp-take-blip@0.2.2). Descriptions and flags come from its manifest. Self-hosted, you hold the credentials.

First call demosend_message

"Send a message to a contact via Take Blip"

tools/callsend_messageresult returned

Tools

What your agent can call.

18 tools, as the package's tools/list returns them.

send_message

Send a message to a contact via Take Blip

get_contacts

List contacts in Take Blip

create_contact

Create a contact in Take Blip

get_threads

Get message threads (recent conversations)

send_notification

Send a notification message to a contact

get_analytics

Get chatbot analytics and metrics

create_broadcast

Create a broadcast distribution list and send messages

get_chatbot_flow

Get chatbot flow/builder configuration

update_contact

Merge/update fields on an existing contact

delete_contact

Delete a contact by identity

get_contact

Get a single contact by identity

get_thread

Get the message thread between the bot and a specific identity

Names and descriptions come from the package's tools/list (@codespar/mcp-take-blip@0.2.2). A kind (read, write, delete) is shown only when the package annotates its tools or each tool was verified one by one; neither exists for this server yet.

Compatibility

MCP is a protocol. Any client that speaks it can mount this server.

The CodeSpar runtime does not route this server. Mount it in your client over stdio · streamable-http.

Protocol

Any MCP client

stdio · streamable-http

Questions

Before you install.

How do I install the Take Blip MCP server?

Run npx -y @codespar/mcp-take-blip@0.2.2 and add the config block above to your MCP client: Claude Code, Cursor, Claude Desktop, VS Code, or any MCP-compatible client. No build step, no SDK required.

What can my agent do with Take Blip?

Take Blip exposes 18 tools for messaging. Your agent calls them directly; the full list is above.

How does Take Blip authenticate, and how are credentials stored?

Take Blip uses API Key. Self-hosted, you hold the credentials: the server reads them from its environment variables.

How does Take Blip handle upstream API changes?

Every server is versioned independently on npm. The command on this page pins 0.2.2, the version whose tools are listed here; your agent keeps running it until you change the version.

Is Take Blip open source? How do I report a bug?

Yes. Take Blip is MIT-licensed and published on npm as @codespar/mcp-take-blip, source on GitHub (link in the Details panel). Report issues on the package repository; security issues go to security@codespar.dev, and we respond within 24 hours.

Pairs well with