AnythingMCP exposes tools and server instructions. The MCP spec also has resources (read-only content the client can attach to context) and elicitation (the server asking the user for input mid-call).
Why they matter here
- Resources: a connector's own setup instructions, the knowledge graph, and an adapter's enum reference cards are all content rather than actions, and are currently forced into tool shape.
- Elicitation: a tool that needs a missing required parameter today fails and hopes the agent retries. Elicitation lets it ask.
Scope: one at a time. Resources first — it has the clearer payoff and no UX design work.
AnythingMCP exposes tools and server instructions. The MCP spec also has resources (read-only content the client can attach to context) and elicitation (the server asking the user for input mid-call).
Why they matter here
Scope: one at a time. Resources first — it has the clearer payoff and no UX design work.