Who it is forA developer or researcher who already works with an AI agent and wants it to manage the knowledge base without using the web interface.
The problemFiling each document by hand in the web interface takes too long when the work is repetitive.
The outcomeAn agent that reads or writes Stru Info content through the MCP interface, limited to the permissions you granted.
What you need first
- A machine that runs Docker and Docker Compose
- PostgreSQL 18, as recommended in the README
- Access to the docs/getting-started.md setup guide and a host port for STRUIINFO_HTTP_PORT
- Optional: a DeepSeek or OpenAI API key stored in an external key file, only if you want AI features
Steps
- Read docs/agent-interface.md and create an agent token with read-only access, or with import, split, tag, and link write access.
- Configure your MCP-capable agent client to point at the Stru Info MCP endpoint described in docs/agent-interface.md. (inferred, check the README)
- Ask the agent to list available documents before it writes anything.
- Review the agent's changes in the 工作台 and confirm them with 确认入库.
Prompt for your agent
In the repo tntexploding/StruInfo, use the MCP interface described in docs/agent-interface.md with a read-only token to list documents matching <topic>. Return the titles and IDs, and verify that no write operation was performed.
Caveat. Agent write access can add or change items, so keep the token scoped and review agent edits in the 工作台 before confirming them.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for tntexploding/StruInfo and "Let an external AI agent file documents through MCP"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer