Within

Query your organization's process index, observations and source documents.

Add to Agentman Studio

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

Resources

What the Within connector does

The Within MCP server connects a Within workspace — a map of how an organization's processes actually run — to Claude, ChatGPT and any MCP-compatible agent. Its 17 tools search a process index, pull the observations and activity timelines behind each process, and read the source documents. Every tool is read-only. Sign-in is OAuth or an API key.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Within tools (17)

  • fetch
  • get_agent_builder_instructions
  • get_agent_builder_resource
  • get_artifact_content
  • get_artifact_details
  • get_hierarchy_node_details
  • get_observation_citation
  • get_process_details
  • get_process_hierarchy
  • get_process_observations
  • get_recent_process_changes
  • list_accessible_workspaces
  • list_sessions
  • search
  • search_artifact_text
  • search_artifacts
  • search_processes

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • No scope boundary exists at consent. Within's RFC 9728 resource descriptor declares scopes_supported as an empty array, and its authorization server advertises four scopes — openid, profile, email and offline_access. Those identify the user and refresh the token; none of them separates one part of the workspace from another. The empty array matters less here than it would on a write-capable server, because the surface it fails to partition is read-only, but a reader should not mistake the sign-in screen for a permission choice.
  • Read-only is current, not guaranteed. Within's limitations page states the tool catalog grows over time and names write tools for safe operations as coming. Verify against the tool reference rather than against this page if the distinction matters to you.
  • One workspace per connection. Within scopes each connection to a single workspace, switched by reconnecting on OAuth or by generating a key in the other workspace. An agent cannot read across two workspaces in one session.
  • get_observation_citation only works for your own sessions. The most detailed evidence tool is restricted to the authenticated user's captures, so a manager cannot pull a colleague's activity timeline through it.
  • Cross-observation analysis is not a tool. Within states that the pattern most teams want — the same workaround appearing across several captures — emerges only by aggregating the observation set, that Within Advisor does this natively, and that over MCP you stitch it yourself by pulling citations and diffing against the pinned process version.
  • Search snippets are not answers. Within's operating principles state that search, search_processes and search_artifacts all return short snippets meant to locate an object, and that an assistant must chain into a get or fetch call before answering. A page or agent quoting a snippet as a finding is misusing the tool by the vendor's own account.
  • There is no cross-document text search. Within states plainly that search_artifact_text works within one artifact and that no cross-document text search exists on the external surface.
  • We could not read tool schemas or safety annotations. The endpoint returned 401 to an anonymous request, so no parameter-level detail or machine-readable safety hint is published here. Parameter names cited above come from Within's documentation.
  • Bulk edits, workspace configuration and user management stay in the UI. Within names all three as out of scope for the MCP.
  • It requires a commercial Within workspace. No free tier is documented.

Frequently asked questions

Can the Within MCP server create or edit a process?

No. Within states that every tool in production is query-only and that the MCP cannot create or modify processes, artifacts, observations or graph entities. All edits happen in the Within UI. This is one of the rare connectors where the vendor's read-only claim survives a name-by-name check of the whole tool list.

What OAuth permissions does the Within MCP server request?

None that narrow anything. Within's resource descriptor declares scopes_supported as an empty array, and its authorization server advertises only openid, profile, email and offline_access. Those are identity claims and token refresh, not permissions over your workspace. Consent grants the whole read surface at once.

How many tools does the Within MCP server have?

Seventeen, and Within publishes all seventeen itself. Anthropic's directory and Within's own tool reference name exactly the same set with no drift in either direction. Within adds that the catalog grows over time and names write tools for safe operations as a direction of travel, so treat seventeen as current rather than permanent.

Why does Within sign-in fail with an authentication error?

Almost always because the MCP has not been switched on for your workspace yet. Within documents a one-time setup in Settings then MCP, where an admin picks the workspace to expose, and warns that both OAuth and Bearer-token requests fail until it is done. Your organization may also need to approve the connector.

What personal data can the Within connector read?

Colleague activity, named and timestamped. Anthropic's directory entry states the connector can see your name and email and list recent workspace sessions including who created them. Within's activity timelines record what a user did, when, and on which systems. Within restricts get_observation_citation to your own sessions.

Can Within send an email or post to Slack?

Not by itself, but its documentation is built around chaining that does. Within publishes a guide pairing its read tools with Gmail, Slack, Linear, Notion, Calendar and Drive connectors, with example prompts that draft mail and post channel summaries. The outbound capability belongs to the second connector; Within supplies the content.

How do I switch between Within workspaces?

At the auth layer, not inside the assistant. Within scopes each connection to one workspace. On OAuth you disconnect the Within connection in your client and reconnect, and the reconnect flow shows a workspace picker. API keys are bound to the workspace that generated them, so you create a new key there and swap the Bearer token.

Is the Within MCP available without a paid Within workspace?

No. Within states plainly that it is a commercial service requiring an active workspace and a provisioned user account, and that the MCP is available to enterprise customers. There is no free or trial tier documented for the connector. Organizations without Within are directed to contact the vendor at hello@within.ai.

Sources

More Productivity connectors

  • 6sense

    Ask an AI agent about 6sense account insights, buying signals and keyword trends.

  • Adobe Workfront

    Find, create, update and delete Workfront work items from an AI agent.

Browse all MCP connectorsClaude and ChatGPT setup guideBrowse AI skills

Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.

Use it in an agent

Put Within to work.

Connect Within once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio