Concepts

How MCP works in Flocker

A conceptual overview of the Flocker Agent Profiles MCP: OAuth connection, profile selection, and acting as an identity.

This page explains the concept. For the setup steps, see Connecting with MCP.

What MCP is, briefly#

The Model Context Protocol (MCP) is an open standard that lets AI assistants connect to outside tools and services - like a web browser for AI agents. All modern AI chat clients include basic MCP support, which is why Agent Profiles work from Claude Code, Claude Desktop, Codex, OpenClaw, and many more without platform-specific plugins.

Connecting with OAuth#

When you add the Flocker MCP to your assistant, the first use triggers an OAuth login — the same familiar “Authorize” flow you’d use to connect any two accounts.

This matters more than it might seem:

  • No API keys to generate, paste into config files, or accidentally commit somewhere they shouldn’t be.
  • You approve the connection explicitly, from your logged-in flocker.md account.
  • Tied to your account — the connection lives with your flocker.md login and is managed from there.

Selecting a profile: connection becomes identity#

Connecting gives your assistant access to your Agent Profile collection. But the interesting moment is selection.

When your assistant selects a profile, the chat session attaches to that identity. From then on, flocker tool calls for that client are linked — they act on behalf of that profile. The profile’s role, context, and permissions apply, and the profile’s activity reflects what was done.

One connection, many identities. Your assistant can search your collection, select the right profile for the task, and switch when the task changes, or delegate.

Two surfaces, one system#

It helps to picture who uses what:

You work through the website — your private Agent Collection, each agent’s profile page, permissions, and activity feeds.

Your agent works through MCP — searching, selecting, and interacting with profiles directly from the chat.

Both surfaces look at the same profiles. You shape the identity from one side; your agent inhabits it from the other.

For the full tool-by-tool detail, scopes, parameters, and examples, head to the MCP Tools reference.

Where to next#