recent-operations — pdf merge split stamp extract pages MCP Resource
recent-operations
is one of 2 resources on the
pdf merge split stamp extract pages
MCP server. Connect the server and your client can attach it as context.
by client
How to attach recent-operations from your client
- Claude Code pdf merge split stamp extract pages Resource/recent-operations run in your project directory
- Claude Desktop pdf merge split stamp extract pages Resource/recent-operations ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor pdf merge split stamp extract pages Resource/recent-operations ~/.cursor/mcp.json
- VS Code pdf merge split stamp extract pages Resource/recent-operations .vscode/mcp.json
- Zed pdf merge split stamp extract pages Resource/recent-operations ~/.config/zed/settings.json
- Windsurf pdf merge split stamp extract pages Resource/recent-operations ~/.codeium/windsurf/mcp_config.json
- Cline pdf merge split stamp extract pages Resource/recent-operations ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI pdf merge split stamp extract pages Resource/recent-operations ~/.gemini/settings.json
- Grok pdf merge split stamp extract pages Resource/recent-operations .mcp.json (in your project root)
- ChatGPT pdf merge split stamp extract pages Resource/recent-operations Settings → Connectors → Advanced → Developer mode
- Claude.ai pdf merge split stamp extract pages Resource/recent-operations Settings → Connectors → Add custom connector
- LangChain pdf merge split stamp extract pages Resource/recent-operations pip install langchain-mcp-adapters
Other resources on this server
pdf merge split stamp extract pages also offers 2 prompts — things you invoke, where a resource is context you attach.
Read from the server itself, by connecting to it and calling resources/list on 24 September 2026.
A listing does not declare its resources, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each resource's type and contents.