agent-stack-mcp

MCP (Model Context Protocol) tooling and integration setups for AWaC workspaces.

Covers both sides of MCP:

• Consuming — connecting a workspace/agent to existing MCP servers.
• Exposing — building and shipping your own remote MCP server that hosted agents (Claude/ChatGPT connectors) authenticate against with OAuth 2.1.

What lives here

• rules/ — use_mcp_tools.md, use_notebooklm_research.md. Conventions for invoking MCP tools and using NotebookLM as a research surface.
• workflows/ — setup-mcp-http-antigravity.md, setup-mcp-http-claude.md, setup-mcp-notebooklm.md. Setup recipes for connecting workspaces to MCP servers.
• skills/ — expose_remote_mcp_server/. How to build and expose an OAuth 2.1 remote MCP server. Encodes two architectural blockers that are invisible until a real connector attempts to connect: the RFC 8707 audience-binding requirement (most OIDC providers cannot satisfy it, so you need an AS shim), and the DNS-rebinding 403 that rejects every authenticated request when the server runs on loopback behind a reverse proxy. Written from a production rollout using Prysm:ID as the identity provider; the recipe is provider-agnostic.

When to include

Add mcp to workspace.yml/stacks whenever the project will either:

• leverage MCP servers (knowledge brains, NotebookLM, Antigravity, etc.) from inside the agent, or
• expose its own MCP server to hosted agents.