Vanmoose Mcp Server
Give your coding agent one npm MCP install that can call screenshots, email, NLP, WHOIS, QR, PDF, and dozens of other utility APIs without wiring each service yourself.
Overview
VanMoose MCP Server is a MCP server for the Build phase that exposes 197 tools across 74 developer APIs so your agent can run screenshots, email, NLP, WHOIS, QR, PDF, and similar utility calls from one integration.
What is this MCP server?
- 197 MCP tools exposed from 74 developer-facing APIs in one stdio npm package (@vanmoose/mcp-server v1.2.1).
- Covers screenshots, transactional email, NLP, WHOIS, QR codes, PDF handling, and related utility workflows.
- Optional TENSCORE_API_KEY unlocks five additional TenScore analytics tools alongside the core VanMoose key.
- stdio transport fits Claude Code, Cursor, Codex, and other local MCP clients with a single VANMOOSE_API_KEY.
- Hosted API gateway model so you avoid maintaining dozens of separate SDKs in your repo.
- 197 MCP tools from 74 developer APIs (server description and schema).
- Package @vanmoose/mcp-server version 1.2.1 with stdio transport.
- Optional TENSCORE_API_KEY enables 5 TenScore analytics tools.
What problem does it solve?
Solo builders waste hours registering separate APIs and writing one-off scripts every time an agent needs email, PDFs, screenshots, or domain checks.
Who is it for?
Indie developers on Claude Code or Cursor who want a single paid API key behind many agent-side automation tasks while building or shipping features.
Skip if: Teams that need only one specific integration with full open-source control, or builders who cannot use npm stdio MCP or a third-party API gateway.
What do I get? / Deliverables
After you install the npm MCP server and add VANMOOSE_API_KEY, your agent can invoke a large catalog of utility operations through standard MCP tool calls instead of custom glue code.
- MCP tool surface of 197 callable operations backed by 74 APIs.
- Agent-ready flows for screenshots, email, NLP, WHOIS, QR, PDF, and related utilities without per-service code.
- Optional TenScore analytics tool access when the second API key is configured.
Recommended MCP Servers
Journey fit
Canonical shelf is Build because the value is wiring many third-party APIs into the agent workspace during product construction. Integrations is the right subphase: this server is a bundled API bridge, not a standalone app feature.
How it compares
Bundled multi-API MCP gateway, not a single-domain agent skill or a curated skills marketplace.
Common Questions / FAQ
Who is VanMoose MCP Server for?
It is for solo and indie builders using AI coding agents who want one MCP install to access screenshots, email, NLP, WHOIS, QR, PDF, and many other APIs without maintaining separate SDKs.
When should I use VanMoose MCP Server?
Use it during Build and Ship when you are wiring automations, generating assets, sending email, or calling utility APIs from Claude Code, Cursor, or Codex instead of hand-rolling HTTP clients.
How do I add VanMoose MCP Server to my agent?
Install @vanmoose/mcp-server from npm, configure stdio MCP in your client, set the required secret VANMOOSE_API_KEY from vanmoose.cc/dashboard, and optionally TENSCORE_API_KEY for the five TenScore tools.