mcp -v2ex

The MCP server mcp-server-v2ex acts as a wrapper around the V2EX official API v2.0. It exposes a set of actions such as fetching notifications, deleting specific notifications, retrieving the current user’s profile via the token, listing nodes, fetching topics under a node, getting topic details, and retrieving topic comments. To use it, first obtain a V2EX API token from https://www.v2ex.com/settings/tokens and place it in the V2EX_API_KEY environment variable. Start the server via the configured MCP entry (the example uses a Node runtime pointing to the dist/index.js of the installed package). Once running, you can invoke the available endpoints through the MCP gateway using the server alias configured (e.g., v2ex). The wrapper handles API calls and returns standard MCP-compatible responses for each action such as notifications, nodes, topics, and comments. The environment also includes an option to disable TLS certificate validation (NODE_TLS_REJECT_UNAUTHORIZED) if you’re behind a MITM proxy or similar network inspection tool.

Prerequisites:

• Node.js (recommended LTS)
• npm (comes with Node.js)

Installation steps:

1. Install the MCP package globally: npm install -g mcp-server-v2ex
2. Ensure you have a valid V2EX API token. You can obtain it from https://www.v2ex.com/settings/tokens
3. Create an MCP configuration entry (as shown in mcp_config) and save it in your MCP manager configuration.
4. Start or reload your MCP server configuration so the new v2ex service is loaded.

Notes:

• If you’re behind a proxy or MITM, you may need NODE_TLS_REJECT_UNAUTHORIZED set to 0 in the env for the MCP entry.
• Ensure the path to the installed package dist/index.js matches your environment if you customize paths.

Tips and common issues:

• Ensure the V2EX_API_KEY is kept secure and not committed in code or logs.
• If you see TLS/SSL certificate errors, you can temporarily set NODE_TLS_REJECT_UNAUTHORIZED to 0, but prefer proper certificate handling in production.
• The MCP server expects the index.js entry from the mcp-server-v2ex package; if you upgrade the package, verify the dist/index.js path remains valid.
• When upgrading Node or the MCP package, test the v2ex service to confirm all endpoints (notifications, tokens, nodes, topics, topic details, and comments) still function as before.