ARCHAI WORLD StudioEnterprise Context MCPDocumentation

Connection Status: ReadySign In Open Studio

ARCHAI ENTERPRISE CONTEXT MCP™

Connect AI Missions to the Context of the Enterprise

ARCHAI Enterprise Context MCP provides a controlled bridge between ARCHAI WORLD Studio and authorized information about an organization’s business, applications, technology, data, risks, controls and ownership.

Streamable HTTPBearer AuthenticationAudited AccessScoped PermissionsScheduled Mission Ready

Start the Connection Explore Resources and Tools

Demonstration Environment

This documentation uses fictional enterprise data. Do not enter confidential, regulated or production information into the demonstration environment.

How the connection works

Four layers separate mission execution, secure access, enterprise information and human accountability.

ARCHAI WORLD Studio

Defines the mission
Selects MCP tools
Schedules execution
Organizes results
Presents findings for human review

Secure MCP Connection

Authenticates the request
Validates permissions
Restricts resources and tools
Records every request
Returns authorized context

Enterprise Context

Business capabilities
Business processes
Applications & technologies
Data entities & AI agents
Risks, controls & owners

Human Decision-Maker

Reviews evidence
Challenges assumptions
Validates information gaps
Approves actions
Remains accountable

ARCHAI WORLD Studio owns and executes the mission. The MCP securely supplies the authorized enterprise context. A human reviews the evidence and makes the decision.

Quick Start

Five steps take a new administrator from portal sign-in to a launched mission.

Sign in to the enterprise portal

Human administrators access the protected portal using email and password.

Portal URL

https://www.archaiworldstudio.com/enterprise-context-mcp/login

EmailPasswordSign In

Security notice: usernames and passwords are for human portal access only. Do not place passwords inside MCP configurations, URLs or mission instructions.

Open Secure Login

Generate an MCP token

After authentication, an Enterprise Admin opens Settings / Connections / Generate Token.

Token nameOrganizationAllowed resourcesAllowed toolsExpiration dateEnvironmentNotes

Token scopes

context:readapplications:readrelationships:readrisks:readcontrols:readowners:readagents:readchanges:readtools:executeaudit:read

The complete token is displayed only once. Copy it and store it securely. ARCHAI WORLD Studio must never display the token inside mission results, screenshots or audit messages.

Configure ARCHAI WORLD Studio

connection.json

{
  "name": "Northstar Enterprise Context",
  "transport": "streamable-http",
  "url": "https://www.archaiworldstudio.com/api/enterprise-context-mcp/mcp",
  "authentication": {
    "type": "bearer",
    "token": "PASTE_TOKEN_SECURELY"
  }
}

1.Open ARCHAI WORLD Studio.
2.Select Connections.
3.Select Add MCP Connection.
4.Enter the connection name.
5.Select Streamable HTTP.
6.Paste the MCP endpoint.
7.Select Bearer Token authentication.
8.Enter the token in the protected credential field.
9.Select Test Connection.
10.Save the connection after verification.

Open ARCHAI WORLD Studio

Test the connection

MCP endpoint

Bearer token

Launch a mission

Mission 002 — The Hidden Dependency

What would stop, degrade or become exposed if the Legacy Credit Decision Engine failed tomorrow?

Affected business capabilitiesDependent processesConnected applicationsTechnology dependenciesData flows at riskOperational and compliance risksExisting controlsAccountable ownersInformation gapsNOW, NEXT and LATER actions

View Mission Example

Authentication

Human sessions and machine connections use two separate, non-interchangeable credential systems.

Human authentication

Used for

Portal administration
Enterprise data management
Token generation
Permission configuration
Audit review
Token revocation

Method: email and password through a secure authenticated session.

MCP authentication

Used for

ARCHAI WORLD Studio connections
Resource discovery
Resource retrieval
Tool execution
Scheduled missions

Header

Authorization: Bearer YOUR_SECURE_TOKEN
Content-Type: application/json

Security requirements

Never include credentials in URLs
Never expose complete tokens in screenshots
Never store tokens in browser localStorage
Never write tokens into audit logs
Use short expiration periods where possible
Assign only the scopes required by the mission
Revoke unused or compromised tokens immediately
Use separate tokens for development, testing and production

MCP Endpoint

https://www.archaiworldstudio.com/api/enterprise-context-mcp/mcp

Streamable HTTPBearer Token

Protocol capabilities

InitializationResource discoveryResource readingTool discoveryTool executionStructured responsesRequest auditing

Generate Token

Available MCP Resources

Eleven read-scoped resources expose the authorized enterprise context, from organization identity to change history.

Organization Profile

context:read

enterprise://organization/profile

Organization identity
Industry
Regions
Business model
Operating context

Business Capabilities

context:read

enterprise://capabilities

Capability name
Criticality
Maturity
Status
Accountable owner

Business Processes

context:read

enterprise://processes

Process description
Supported capability
Criticality
Recovery objective
Owner
Supporting applications

Applications

applications:read

enterprise://applications

Application name
Purpose
Lifecycle status
Criticality
Deployment model
Business owner
Technology owner
Recovery objectives
Sensitive data indicator

Technologies

context:read

enterprise://technologies

Technology name
Category
Version
Vendor
Support status
End-of-support date
Hosting environment
Risk level

Data Entities

context:read

enterprise://data

Data entity name
Classification
Personal information indicator
System of record
Retention period
Data owner

AI Agents

agents:read

enterprise://ai-agents

Agent purpose
Autonomy level
Allowed actions
Prohibited actions
Data access
Decision limit
Human approval requirement
Accountable owner
Shutdown owner
Monitoring status

Risks

risks:read

enterprise://risks

Risk description
Category
Likelihood
Impact
Rating
Owner
Related entity

Controls

controls:read

enterprise://controls

Control description
Control type
Status
Effectiveness
Owner
Last test date
Evidence reference

Owners

owners:read

enterprise://owners

Name
Role
Department
Accountability status
Owned entities

Use fictional names and example.com email addresses only.

Relationships

relationships:read

enterprise://relationships

Capability supported by process
Process supported by application
Application depends on application
Application uses technology
Application processes data
AI agent accesses data
AI agent invokes application
Risk affects application
Control mitigates risk
Owner accountable for entity

Changes

changes:read

enterprise://changes

Entity changed
Change type
Previous value
Current value
Timestamp
Change source
Verification status

This resource is especially important for recurring and scheduled missions.

Available MCP Tools

Eight tools let ARCHAI WORLD Studio search context, trace dependencies, assess impact and generate executive briefs.

Evidence Classification

Every mission finding must be labeled by how it was derived — never presented as more certain than it is.

Evidence

Information directly supported by an authorized enterprise record.

Inference

A conclusion logically derived from available evidence but not explicitly recorded.

Assumption

A belief or working hypothesis that has not been validated.

Information Gap

An important question that cannot be answered with the available enterprise context.

ARCHAI WORLD Studio must never present an inference, assumption or information gap as confirmed enterprise evidence.

Every mission finding should include:

ClassificationSource resourceSource recordLast verified dateConfidenceRetrieval timestamp

Mission Examples

Mission 002

The Hidden Dependency

What would stop, degrade or become exposed if the Legacy Credit Decision Engine failed tomorrow?

Tools used

search_enterprise_contextget_application_dependenciesassess_business_impactgenerate_executive_brief

Resources used

enterprise://capabilitiesenterprise://processesenterprise://applicationsenterprise://technologiesenterprise://dataenterprise://risksenterprise://controlsenterprise://ownersenterprise://relationships

Seven business impactsThree critical dependenciesTwo high risksThree information gapsExecutive findingRequired decisionNOW, NEXT and LATER actions

Representative fictional result. Actual mission outputs depend on the authorized enterprise context available at execution time.

Mission 004

The AI Agent Approval

Is the Customer Credit AI Agent ready for enterprise approval?

Tools used

search_enterprise_contextassess_ai_agent_readinessgenerate_executive_brief

Expected decision:APPROVE WITH CONDITIONS

Required conditions

Confirm accountable owner
Set decision limits
Test human escalation
Verify audit trail
Confirm shutdown authority
Validate monitoring

Representative fictional result. The decision does not constitute legal, compliance or certification advice.

Scheduled Missions

ARCHAI WORLD Studio owns and triggers the schedule. ARCHAI Enterprise Context MCP provides current authorized context at execution time. There is only one scheduler.

Schedule options

Run onceDailyWeeklyMonthlyCustom scheduleAfter a recorded architecture changeBefore a governance review

Scheduled mission fields

Mission nameMCP connectionTarget entityFrequencyTimeTime zoneOutput formatNotification destinationHuman reviewerActive or paused

Output formats

Executive BriefJSONCSVMarkdown

scheduled-mission.json

{
  "mission_name": "Weekly Architecture Change Watch",
  "connection": "Northstar Enterprise Context",
  "frequency": "weekly",
  "day": "monday",
  "time": "08:00",
  "timezone": "America/New_York",
  "tool": "get_changes_since",
  "output": "executive_brief",
  "human_review_required": true
}

Permissions and Scopes

Grant the minimum access required for the mission. Token permissions must be evaluated server-side for every resource request and tool execution.

Scope	Resource or Tool	Recommended Role
context:read	Business capabilities, processes, organization profile	Enterprise Architect
applications:read	Applications	Enterprise Architect
relationships:read	Relationships	Enterprise Architect
risks:read	Risks	Risk Manager
controls:read	Controls	Risk Manager
owners:read	Owners	Enterprise Admin
agents:read	AI agents	AI Governance Manager
changes:read	Change history	Read-Only Analyst
tools:execute	All 8 MCP tools	ARCHAI WORLD Studio Token
audit:read	Audit trail	Enterprise Admin

Audit Trail

Every connection and mission interaction is recorded.

Audit events

Login
Token generation
Token revocation
Connection test
Resource discovery
Resource read
Tool execution
Failed authentication
Mission execution
Data export

Audit fields

Timestamp
Organization
User or token name
Action
Resource or tool
Status
Request ID
Duration
Environment

Never log

Passwords
Complete tokens
Confidential payloads not required for the audit record

Security Principles

Separate human credentials from machine credentials
Use scoped, expiring and revocable tokens
Validate authorization on the server
Isolate organizations and environments
Record MCP requests and tool executions
Never expose secrets in URLs
Never display complete tokens after creation
Separate demonstration and production environments
Require human review for consequential decisions
Treat missing information as an information gap
Test backup and token-revocation procedures

Do not connect the demonstration environment to real confidential, regulated or production data.

Troubleshooting

Frequently Asked Questions

FICTIONAL ENTERPRISE DEMONSTRATION

Ready to Connect Enterprise Context to an AI Mission?

Connect ARCHAI WORLD Studio to the Enterprise Context MCP, verify the available resources and launch your first governed mission.

Connect ARCHAI WORLD Studio Generate Access Token View Mission Examples

Not a chatbot. A connected enterprise mission.

Connect AI Missions to the Context of the Enterprise

How the connection works

ARCHAI WORLD Studio

Secure MCP Connection

Enterprise Context

Human Decision-Maker

Quick Start

Sign in to the enterprise portal

Generate an MCP token

Configure ARCHAI WORLD Studio

Test the connection

Launch a mission

Authentication

Human authentication

MCP authentication

MCP Endpoint

Available MCP Resources

Organization Profile

Business Capabilities

Business Processes

Applications

Technologies

Data Entities

AI Agents

Risks

Controls

Owners

Relationships

Changes

Available MCP Tools

search_enterprise_contextcontext:read

get_application_dependenciesapplications:read

assess_business_impactcontext:read

find_ownership_gapsowners:read

assess_ai_agent_readinessagents:read

find_technology_risksrisks:read

get_changes_sincechanges:read

generate_executive_brieftools:execute

Evidence Classification

Evidence

Inference

Assumption

Information Gap

Mission Examples

The Hidden Dependency

The AI Agent Approval

Scheduled Missions

Permissions and Scopes

Audit Trail

Security Principles

Troubleshooting

401 Unauthorized

403 Forbidden

404 Resource Not Found

429 Too Many Requests

MCP Initialization Failed

Empty Mission Result

Frequently Asked Questions

Does ARCHAI WORLD Studio receive my username and password?

Does the MCP give the Studio access to everything?

Where are missions scheduled?

Can access be revoked?

Can the Studio make enterprise decisions automatically?

What happens when information is missing?

Is the demonstration using a real financial institution?

Ready to Connect Enterprise Context to an AI Mission?