Server facts
pluggedin-mcp
Project
- Author
- VeriTeknik
- Repository
- github.com/VeriTeknik/pluggedin-mcp
- License
- Not specified
- Category
- MCP Gateways & Proxies
Tech
- Runtime / language
- Not specified
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 52
- Last commit
- Data as of
Tags
- Proxy
- mcp
- middleware
Overview
Configurations stored in the plugged.in App determine which tools, resources, resource templates, and prompts the proxy exposes. It retrieves these capabilities through App APIs, uses prefixes to distinguish them by server, and forwards requests to the matching server. A discovery tool asks the App to discover capabilities for configured servers. For document work, users can ask questions of their knowledge base and receive answers with document sources, then search their library and use returned document IDs to retrieve full text. They can also create, update, or append to AI-generated documents.
Session memory follows a capture-and-retrieval workflow: start a session, record observations, and end it to generate an AI-compressed summary. Semantic searches return compact memory matches, while a separate details tool retrieves complete entries. Clipboard tools manage named values and indexed entries, with push and pop operations for ordered workflows. Notifications can be sent with optional email delivery, filtered when listed, marked done, or deleted. The setup tool supplies API key guidance without requiring a key itself, and the App supports workspaces for switching between configuration sets.
pluggedin-mcp setup notes
- pluggedin-mcp records stdio only; confirm a network transport upstream before planning remote access.
- pluggedin-mcp has no recorded license; confirm reuse terms in its repository.