CodeIssuesDiscussionsWikiPull RequestsProjectsCommitsActionsReleasesContributorsPulse● GatesSecuritySettingsDeploymentsPipelineInsightsAgents✨ Explain✨ Ask AI✨ Workspace✨ Spec✨ Tests▓ Debt Map✨ NL Search🏛 Archaeology
Blame · Line-by-line history
ANTHROPIC_DIRECTORY_SUBMISSION.md
Each line is annotated with the commit that last touched it. Click any SHA to jump to that commit and see the surrounding change.
| 16c3343 | 1 | # Anthropic Connector Directory — submission package (prepared 2026-07-14) |
| 2 | ||
| 3 | Everything needed to submit Gluecron to the Claude connectors directory. | |
| 4 | Submission happens in **claude.ai → admin settings → connector directory** | |
| 5 | and requires a **Team or Enterprise** org, submitted by the org owner. | |
| 6 | (Guide: https://support.claude.com/en/articles/12922490-remote-mcp-server-submission-guide) | |
| 7 | ||
| 8 | ## Connector details (paste into the form) | |
| 9 | ||
| 10 | | Field | Value | | |
| 11 | |---|---| | |
| 12 | | Name | Gluecron | | |
| 13 | | Description | AI-native git hosting — repos, PRs, issues, CI gates, and AI code review over MCP (60 tools). | | |
| 14 | | Remote MCP URL | `https://gluecron.com/mcp` (streamable HTTP) | | |
| 15 | | Authentication | OAuth 2.0 with **dynamic client registration** (RFC 7591) — no static client ID needed. Authorization-code + PKCE; 1-hour access tokens with 30-day rotating refresh; RFC 6750 `invalid_token` signaling. Also accepts personal access tokens as Bearer. | | |
| 16 | | OAuth discovery | `https://gluecron.com/.well-known/oauth-authorization-server` and `/.well-known/oauth-protected-resource` (both live) | | |
| 17 | | Privacy policy | `https://gluecron.com/privacy` | | |
| 18 | | Terms | `https://gluecron.com/terms` | | |
| 19 | | Docs / agent map | `https://gluecron.com/llms.txt`, `https://gluecron.com/connect/claude-guide` | | |
| 20 | | Geographic availability | Global — no restrictions | | |
| 21 | ||
| 22 | ## Ownership verification | |
| 23 | ||
| 24 | We own the domain, API, and all resources the connector touches. Domain | |
| 25 | control is independently provable: `com.gluecron/gluecron` is published on | |
| 26 | the official MCP Registry (registry.modelcontextprotocol.io), which required | |
| 27 | cryptographic domain verification via | |
| 28 | `https://gluecron.com/.well-known/mcp-registry-auth`. | |
| 29 | ||
| 30 | ## Tool annotations (directory requirement) | |
| 31 | ||
| 32 | All **60 tools** carry MCP `ToolAnnotations` served on `tools/list` | |
| 33 | (deployed 2026-07-14, commit `523ddad`): | |
| 34 | - 26 read-only (`readOnlyHint: true`) — search, read, health, explain, status | |
| 35 | - 27 non-destructive writes — create PR/issue/branch/file, comments, labels | |
| 36 | - 7 destructive (`destructiveHint: true`) — delete_repo, delete_file, | |
| 37 | merge_pr, close_pr, close_issue, cancel_workflow_run, update_repo | |
| 38 | ||
| 39 | ## Reviewer test account + runbook | |
| 40 | ||
| 41 | Account: **`anthropic-reviewer`** (created 2026-07-14; credentials supplied | |
| 42 | in the submission form by the owner — never committed here). Pre-populated | |
| 43 | with the public repo **`anthropic-reviewer/sample-api`** containing source | |
| 44 | files, an open issue, and an open pull request. | |
| 45 | ||
| 46 | Suggested reviewer runbook: | |
| 47 | 1. Add `https://gluecron.com/mcp` as a custom connector → Claude is | |
| 48 | challenged with the OAuth flow → sign in as `anthropic-reviewer`. | |
| 49 | 2. `gluecron_repo_search {query:"sample"}` → returns `sample-api` (read-only). | |
| 50 | 3. `gluecron_repo_read_file {owner:"anthropic-reviewer", repo:"sample-api", path:"README.md"}`. | |
| 51 | 4. `gluecron_create_issue` on `sample-api` → issue appears at | |
| 52 | `https://gluecron.com/anthropic-reviewer/sample-api/issues`. | |
| 53 | 5. `gluecron_create_pr` from the seeded feature branch → then | |
| 54 | `gluecron_merge_pr` (annotated destructive) to see gate enforcement. | |
| 55 | 6. Revoke access at `https://gluecron.com/settings/applications`. | |
| 56 | ||
| 57 | ## Usage-policy notes | |
| 58 | ||
| 59 | - No financial transactions, no media generation, no conversation-data | |
| 60 | extraction. The connector operates only on git repositories the | |
| 61 | authenticated user owns or has been granted access to. | |
| 62 | - Destructive tools are annotated and additionally gated server-side by | |
| 63 | per-repo write/admin ACLs and branch-protection/merge gates. | |
| 64 | ||
| 65 | ## Submission-day checklist | |
| 66 | ||
| 67 | - [ ] Finish seeding `sample-api` (feature branch + open PR) — needs any PAT | |
| 68 | - [ ] Org owner submits via claude.ai admin settings with the reviewer creds | |
| 69 | - [ ] Record the submission ticket/reference here |