workos-github-mcp-server

Provides an MCP server that exposes WorkOS GitHub-related functionality to AI agents via the Model Context Protocol, enabling tools/actions against GitHub (as supported by the underlying WorkOS GitHub integration).

Evaluated Apr 04, 2026 (40d ago)
Homepage ↗ Repo ↗ DevTools mcp agents workos github developer-tools automation api-integration
⚙ Agent Friendliness
40
/ 100
Can an agent use this?
🔒 Security
64
/ 100
Is it safe for agents?
⚡ Reliability
25
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
55
Documentation
40
Error Messages
0
Auth Simplicity
50
Rate Limits
20

🔒 Security

TLS Enforcement
90
Auth Strength
70
Scope Granularity
45
Dep. Hygiene
50
Secret Handling
60

Assessed conservatively: TLS is assumed for any production-grade API connectivity, while auth/secrets handling and dependency hygiene are not verifiable from the provided content. Prefer least-privilege credentials and avoid logging MCP configuration/headers.

⚡ Reliability

Uptime/SLA
0
Version Stability
50
Breaking Changes
30
Error Recovery
20
AF Security Reliability

Best When

You already use WorkOS and want to connect an MCP-enabled agent runtime to GitHub-related capabilities via standard tool calls.

Avoid When

You require complete GitHub API coverage or need REST/GraphQL endpoints for your own non-agent clients; this package is specifically for MCP tool integration.

Use Cases

  • Let an AI agent perform GitHub workflows (e.g., repo/org-related operations) through a standard MCP tool interface
  • Automate internal developer operations that involve GitHub configuration or resource inspection using agent tool calls
  • Build agentic workflows that need GitHub data/actions without writing custom GitHub integration code

Not For

  • Direct human browsing of GitHub resources (this is an agent integration layer)
  • High-complexity enterprise authorization flows that require custom, per-tenant identity orchestration beyond what WorkOS supports
  • Use as a general GitHub API wrapper unless the MCP server explicitly exposes the needed operations

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
No
Webhooks
No

Authentication

Methods: WorkOS API key (typical WorkOS pattern) Provider-specific credentials as required by the GitHub integration
OAuth: No Scopes: No

Exact auth method(s) and any scope model are not provided in the supplied content, so assessed at a conservative level based on typical WorkOS MCP/API patterns.

Pricing

Free tier: No
Requires CC: No

Pricing details not included in the provided material; MCP server usage likely depends on WorkOS plan/pricing.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • Agents may need careful handling of rate limits or transient failures from the underlying WorkOS/GitHub APIs
  • If tool outputs are paginated upstream, the agent may require explicit pagination parameters (not confirmed from provided content)
  • MCP servers sometimes expose a subset of operations; the agent may attempt unsupported tools if names/capabilities aren’t clearly documented

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for workos-github-mcp-server.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-04-04.

8642
Packages Evaluated
17761
Need Evaluation
586
Need Re-evaluation
Community Powered