Productivity · Local MCP server
Agentrender MCP
URL to screenshot, PDF, or structured extract for AI agents via MCP.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.corbinvachal48/agentrender-mcp- Version
- 0.1.0
- Status
- Active
- Category
- productivity
- Transport
- stdio (local process)
- Package
- PyPI
- Published
- 2026-09-08
- Updated
- 2026-09-08
- Publisher
- corbinvachal48 (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/corbinvachal48) · how
- Listed under
- PDF MCP servers
- Repository
- github.com/corbinvachal48/agentrender-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| PyPI | agentrender-mcp | 0.1.0 | stdio |
How to connect Agentrender MCP
Agentrender MCP runs locally from a Python package published to PyPI: agentrender-mcp version 0.1.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install - the usual command is uvx agentrender-mcp. It reads these environment variables: AGENTRENDER_API_KEY (required, secret) and AGENTRENDER_BASE_URL; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"agentrender-mcp": {
"command": "uvx",
"args": [
"agentrender-mcp"
],
"env": {
"AGENTRENDER_API_KEY": "<secret>",
"AGENTRENDER_BASE_URL": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More productivity servers
| Server | Runs |
|---|---|
| AgentPayX402 micropayments MCP: Xiaohongshu notes and paid APIs settled in USDC on Base. | Remote & Local · HTTP, stdioLive check: ✗ no handshake |
| AgentPay (all tools)Pay-per-call web extract, DNS/WHOIS/IP lookup, PDF/RSS/sitemap tools. x402 USDC on Base/Algorand. | Remote · HTTPLive check: ✓ handshake |
| AgentPay Doc ToolsPay-per-call PDF to text, RSS/Atom to JSON, sitemap to URLs for agents. x402 USDC, Base/Algorand. | Remote · HTTPLive check: ✓ handshake |
| AgentPingLet your AI agent notify you by email, Slack, Discord, or webhook. One tool: send_notification. | Remote · HTTPLive check: sign-in required |
| AgentsProgrammatic control of the Hiro security platform: scans, tasks, plans, and approvals. | Remote · HTTPLive check: sign-in required |
| agentsbase - Email for AI AgentsEmail for AI agents. Create mailboxes, send/receive emails, and auto-extract verification codes. | Local · stdio |
| AgentSiteTask-first cross-agent collaboration for discussions, review, referrals, and reusable knowledge. | Remote · HTTPLive check: ✓ handshake |
| AgentsporeConnect an AI agent to AgentSpore: receive tasks, report progress, and message other agents. | Local · stdio |