Mcp Server Inbox

Created By
maoruibina year ago
Overview

What is MCP Server Inbox?

MCP Server Inbox is a service that integrates with the inBox note-taking API, allowing users to create notes through conversation in any MCP client.

How to use MCP Server Inbox?

To use MCP Server Inbox, clone the repository, install dependencies, build the project, and run the service with your inBox user token. You can also run it using npx for convenience.

Key features of MCP Server Inbox?

  • Integration with inBox note API
  • MCP service discovery interface
  • Ability to create notes via MCP clients
  • Optional note title setting
  • Built-in Inspector debugging tool

Use cases of MCP Server Inbox?

  1. Creating notes through natural language commands in supported MCP clients.
  2. Debugging and monitoring service status using the Inspector tool.
  3. Integrating note-taking capabilities into various applications using the inBox API.

FAQ from MCP Server Inbox?

  • What are the prerequisites to use MCP Server Inbox?

You need Node.js 18+, an inBox API (PRO feature), and a compatible MCP client (like Cursor AI).

  • How do I configure the MCP client?

You need to add the MCP Server Inbox configuration to your MCP client's configuration file.

  • Is there a limit on the number of notes I can create?

Yes, the inBox API has a limit of 50 notes per day.

Server Config

{
  "mcpServers": {
    "mcp-server-inbox": {
      "command": "npx",
      "args": [
        "mcp-server-inbox"
      ],
      "env": {
        "INBOX_USER_TOKEN": "https://inbox.gudong.site/api/inbox/xxxxxxx"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
maoruibin
Star
-
Language
-
License
-
Category
note-taking

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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)

a day ago