Request Triage MCP Server
Allows managing a Notion database of automation requests, including listing pending requests, saving priority scores with rationale, and retrieving ranked backlogs.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Request Triage MCP Serverlist pending requests"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Request Triage Agent
Most of the "AI agent" projects I'd built before this were really just RAG pipelines with extra steps; just ask a question, retrieve some context, get an answer back. Nothing was actually deciding anything. This one does: give it a pile of automation requests from different teams and it works out, on its own, which ones matter most and why.
What it does
Feed it a backlog of requests sitting in a Notion database eg "Sales wants X," "Support wants Y," each tagged with a rough urgency and effort. Point the agent at it, and it scores every request, writes a short rationale for each score, and hands back a ranked list. Nobody told it the order of operations, it figures out by itself.
Related MCP server: Notion Weaver
How it works
Three tools, exposed through an MCP server:
list_pending_requests— pull everything still waiting to be triagedsave_priority_score— write a score (1-100) and a one-line rationale back to a requestget_ranked_backlog— pull the final ranked list once everything's scored
Claude gets the goal and those three tools, nothing else. It calls whichever one it needs, looks at what comes back, and decides the next move. This loop is the whole project. agent.py is basically that loop and nothing more.
Notion is just the system of record here, not the point. Swap it for a database or a Slack channel and the agent logic doesn't change. This is the actual value of building it on MCP instead of writing one-off glue code to Notion's API directly in the agent.
Stack
Claude (Sonnet) for the reasoning
MCP (
mcpPython SDK) for the tool layer; server inmcp_server.py, client/loop inagent.pyNotion API for storage (raw REST calls in
notion_helper.py, no SDK; wanted to see the actual request/response shape)
Running it
pip install -r requirements.txt
cp .env.example .env # fill in your Anthropic key + Notion integration token + database ID
python notion_helper.py # seeds a handful of sample requests
python agent.py # watch it triage themYou'll need a Notion integration with access to a database that has these columns: Request (title), Team (select), Urgency (select), Effort (select), Status (select: Pending/Scored), Priority Score (number), Rationale (text).
Why
I wanted to actually build something that takes actions instead of just answering questions, and prioritization-under-competing-demands felt like the most honest test of that; it's a real problem and "here's my reasoning for the ranking" is a much better answer than a black-box score.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/AgnesMuita/AI-operations-triage-agent'
If you have feedback or need assistance with the MCP directory API, please join our Discord server