Native connectors
Start with Claude-supported read/search access where the customer's admin and users approve the right scopes.
Connector guide
Claude connectors and governance guide
A practical guide to native Claude connectors, BlueSky-hosted MCP connectors, custom connector scoping, OAuth review, write-action gates, and Agentic OS upgrade discovery.
MCP connectors
Use BlueSky-hosted MCP when the workflow needs governed tools, tenant allowlists, audit events, and human approval for writes.
Custom builds
Use paid scoping when the source system, auth model, data classes, or write actions need a dedicated implementation plan.
Classify before connecting
The customer should know what kind of connector they are enabling before they approve access. Classification keeps simple native connectors fast and high-risk custom work properly scoped.
Read/search first
Prefer read-only or search-only access for early pilots so the team can prove value without changing business systems.
Write-action controls
Any connector that creates, updates, or deletes records needs business-owner approval, human review, and audit visibility.
Data classes
Document whether the connector touches customer data, employee data, regulated data, financial data, or source code.
How connector demand becomes Agentic OS
Repeated manual workflows discovered during rollout are often better handled as governed automations than one-off prompt habits. Launchpad captures those signals and routes them into BlueSky follow-up.
Workflow pattern
Track the repeated task, source systems, approvals, business owner, and expected outcome.
Risk screen
Separate safe assistive workflows from actions that need approvals, test data, rollback, or change-control review.
Upgrade path
Qualified workflows become MCP connector candidates, custom connector projects, or Agentic OS pilots.
Implementation checklist
These are the decisions BlueSky wants settled before a rollout becomes harder than it needs to be.
- 1List target systems and business owners.
- 2Classify each connector as native Claude, BlueSky-hosted MCP, or custom build.
- 3Document auth model, OAuth scopes, data classes, and write actions.
- 4Start with read/search access when possible.
- 5Require human approval for write-capable tools.
- 6Capture audit and usage evidence during the pilot.
- 7Route repeated high-value workflows into Agentic OS discovery.
Common questions
Should every connector become a custom project?
No. Native Claude connectors should stay native when they meet the use case. Custom work is for source systems, auth models, controls, or workflows that native connectors cannot handle.
When should a connector require human approval?
Any connector that changes a business system should require human approval, clear ownership, scope review, and audit visibility before broad use.
How does connector rollout create Agentic OS opportunities?
Connector pilots reveal repeated work. When that work has clear inputs, decisions, approvals, and outcomes, it becomes a candidate for a governed automation pilot.
References and next steps
Official Claude documentation remains the source of truth for current plan capabilities and setup screens.