mcpspinner-api

Created By
devendershekhawata year ago
API component for mcpspinner - unified access to MCP servers with a single API key
Overview

what is mcpspinner-api?

mcpspinner-api is an API component that provides unified access to multiple MCP (Model Context Protocol) servers using a single API key, simplifying integration for developers.

how to use mcpspinner-api?

To use mcpspinner-api, install the dependencies using Poetry, and run the development server with the provided command. You can then access various MCP servers through the unified API.

key features of mcpspinner-api?

  • Single API Key for all MCP server access
  • Unified Interface for consistent API usage
  • Secure Credential Management for user credentials
  • Supports multiple MCP servers including GitHub, Slack, Discord, and Linear.

use cases of mcpspinner-api?

  1. Integrating multiple communication platforms (like Slack and Discord) into a single application.
  2. Managing user credentials securely across different services.
  3. Simplifying API access for developers working with various MCP servers.

FAQ from mcpspinner-api?

  • What is an MCP server?

MCP stands for Model Context Protocol, which allows for integration with various services.

  • How do I get an API key?

You can obtain an API key by following the setup instructions in the documentation.

  • Is mcpspinner-api free to use?

Yes, mcpspinner-api is open-source and free to use under the MIT License.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
devendershekhawat
Star
0
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
Voyei

4 hours ago