Tembo MCP Server

Created By
tembo-ioa year ago
MCP server for Tembo Cloud's platform API
Overview

what is Tembo MCP Server?

Tembo MCP Server is a server designed for the Tembo Cloud platform API, enabling seamless integration and interaction with the cloud services provided by Tembo.

how to use Tembo MCP Server?

To use the Tembo MCP Server, you can install it via Smithery or clone the repository and configure it with your API key for Tembo Cloud.

key features of Tembo MCP Server?

  • Easy installation via Smithery CLI
  • Local setup instructions provided
  • Configuration for API key integration

use cases of Tembo MCP Server?

  1. Integrating cloud services into applications using the Tembo API.
  2. Developing applications that require cloud-based data processing.
  3. Facilitating communication between local applications and the Tembo Cloud.

FAQ from Tembo MCP Server?

  • How do I install the Tembo MCP Server?

You can install it using the Smithery CLI or clone the repository and follow the setup instructions.

  • Is there a hosted version available?

A hosted version is coming soon.

  • What do I need to run the server locally?

You need to clone the repo, download Claude Desktop, and configure it with your Tembo API key.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
tembo-io
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago