More context. Not more guesswork.

Understand the protocol before connecting it.

An MCP server exposes resources and tools to a client. A tool call can affect real systems, so every integration needs explicit permissions, scoped credentials and user-visible outcomes.

• Resources provide context; tools perform defined actions.
• Read-only access should be separate from write permissions.
• Credentials must never appear in prompts or browser bundles.

A roadmap, not an API reference.

Potential directions include project-context resources and permissioned development tools. No endpoint, SDK, tool schema or agent execution feature is available to integrate with.

• Pending: supported tool definitions and authentication.
• Pending: approval, logging and access controls.
• Pending: a functioning generation engine before agentic workflows.