io.github.sajeetharan由 GitHub 帳號 sajeetharan 發布v1.5.1更新於 Nov 3, 2026
The open-source talent graph for humans and AI agents. Find developers.
以 DevGlobe 開源人才圖譜為基礎的託管 MCP 端點，讓助理搜尋公開開發者檔案並發起需經本人同意的引薦。
Web executable，透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。
把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式，或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南，先向你展示發布者、端點和登入方式，經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。
閱讀 https://sourceweft.com/mcp/io.github.sajeetharan%2Fdevglobe/install.md，並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前，先告訴我它的發布者、端點和登入方式，等我確認。不要把 API 金鑰寫進命令或我會提交的檔案；問我金鑰應從哪裡取得。把它新增到你客戶端的 mcpServers 設定中。
{
"mcpServers": {
"devglobe": {
"type": "http",
"url": "https://www.devglobe.dev/mcp"
}
}
}The open-source talent graph for humans and AI agents.
[Live Demo] [Documentation] [VS Code] [GitHub Stars] [GitHub Sponsors] [License] [PRs Welcome]
[DevGlobe Demo]26,000+ developers · ranked by stars, commits, repo reach & StackOverflow reputation · searchable by skill, location & language
DevGlobe is the open-source talent graph for humans and AI agents. It combines a 3D developer map with Azure Cosmos DB vector and hybrid search to surface relevant expertise from real contribution signals rather than popularity alone. The long-term vision is a consent-aware discovery layer where AI agents can find the right human collaborators.
The dynamic application is hosted on Azure Container Apps. Product, API, MCP, Agent Skill, and agent-readiness documentation is published separately on GitHub Pages.
[!IMPORTANT] Connect an AI agent to DevGlobe: MCP-compatible agents can use the hosted endpoint at
https://www.devglobe.dev/mcpto search public developer profiles without credentials. Verified agents can also request developer-approved introductions. See the MCP setup guide.Show up while you code: Install DevGlobe: Live Coding Globe, choose Go Live, and appear on the globe while building private coding stats. The extension never reads source code, file paths, repositories, branches, or keystrokes.
The app automatically falls back to the bundled sample data (20 developers) when no Cosmos DB credentials are configured. No API keys, no emulator, no setup — just clone and run.
Text search works fully offline. Vector/hybrid search requires Azure OpenAI (see Option 3).
For contributors working on the API layer or data pipeline:
Install the Cosmos DB Emulator — Download here (Windows, macOS via Docker, or Linux Docker)
Start the emulator and wait for it to be ready at https://localhost:8081
Seed sample data into the emulator:
Create .env.local (the seed script prints this for you):
Run the app:
The emulator key above is Microsoft's well-known emulator key — it is intentionally public and only works locally.
For the complete experience including AI-powered search:
AZURE_OPENAI_CHAT_DEPLOYMENT enables generated fun facts on identity cards. Cards use factual profile copy when the chat deployment is unavailable.
Production serves the Next.js application from Azure Container Apps, high-volume public API reads from Azure Functions, and the developer snapshot from Azure Blob Storage. See docs/azure-backend.md for the resource layout, environment switches, and deployment checks.
All dimensions are log-normalized to prevent outlier domination.
Requires API keys — copy .env.example to .env and fill in your tokens.
Verified community credentials are stored explicitly on each developer document. Do not infer them from stars, followers, or profile text.
Supported IDs: github-star, microsoft-mvp, google-developer-expert, docker-captain, cncf-ambassador, aws-hero, and aws-community-builder. The legacy docker-champion ID remains supported. The upload script preserves this field from source JSON, and the list, detail, and search APIs project it from Cosmos DB.
Populate exact GitHub-login matches from the official GitHub Stars, Google Developer Experts, and CNCF Ambassadors rosters:
The command preserves existing tags and is idempotent. Other credentials require an official profile that explicitly identifies the developer's GitHub account; do not populate them by matching display names.
Pushes to main build the standalone Next.js image in Azure Container Registry and deploy it to Azure Container Apps through GitHub Actions OIDC. The deployment identity requires Contributor access scoped to the application resource group and these repository variables: AZURE_CLIENT_ID, AZURE_TENANT_ID, and AZURE_SUBSCRIPTION_ID.
Required environment variables:
Lifecycle emails are transactional and best-effort. Claims use the verified primary email authorized through GitHub OAuth; self-nominations collect an explicitly consented notification address. Addresses are stored only in the private developer-contacts container and are never projected by public APIs or copied into developer documents. Create the container before deployment:
See the lifecycle email PRD.
Claimed-profile visibility insights use allow-listed engagement events with hashed session IDs. Create the TTL-enabled container before deployment with node scripts/setup-engagement-container.js. See the engagement analytics contract for event semantics, privacy thresholds, and deletion behavior.
Claimed developers can also configure personalized open-source contribution recommendations. Candidates come only from public, fresh, unassigned GitHub issues in repositories with contribution guidance. Create the shared quota-state container with node scripts/setup-contribution-state-container.js before deployment. See the contribution opportunities contract.
Verified users can explicitly opt in to a Monday weekly digest from the user menu. The first run records a private comparison baseline without sending email; later messages require rank movement, a fresh contribution opportunity, or a pending introduction request and include an attributed deep link to the relevant action. The Azure Functions app invokes /api/cron/weekly-digest at 13:00 UTC each Monday; only verified contacts with productUpdatesEnabled: true are eligible. Each message uses a per-user, per-week idempotency key and includes one-click unsubscribe headers and a signed unsubscribe link.
Generate a manual-review activation queue and weekly social spotlight from public, unclaimed profiles:
The command is read-only against Cosmos DB and never sends messages or retrieves private contact details. Review each draft before contacting a developer through an appropriate public channel.
The Activity tab is anonymous and shows a rolling 24-hour feed for indexed developers. Create its dedicated Cosmos container before deployment:
Deploy functions/activity-ingest as an Azure Timer Function and configure these application settings:
The timer invokes the collector every minute, matching GitHub's advertised polling interval. GitHub's public Events API is best-effort and may delay or omit events; the 15-second browser refresh does not guarantee GitHub source delivery within that interval. A valid GITHUB_TOKEN is required for full three-page collection; anonymous fallback inspects one page only. The Cosmos activity container uses a 48-hour TTL while the API exposes only the latest 24 hours.
The /space globe receives an opt-in heartbeat from the DevGlobe editor extension every 30 seconds while the developer is active. Heartbeats pause after one minute without editor activity. Presence is live for 90 seconds and remains visible as recently coding for up to 15 minutes. Developers can optionally share a bounded coding status, explicitly name a coding agent and model, join a 25- or 50-minute focus session, and receive rate-limited waves from signed-in users. Focused developers using the same language form temporary globe connections, and stopping presence returns a private companionship recap. Daily coding totals, streaks, achievements, language time, and editor time are derived only from consecutive valid heartbeats and are visible only to the signed-in developer. DevGlobe does not infer agent usage or collect source code, file paths, repositories, branches, prompts, responses, model traffic, or keystrokes for this feature.
Provision both TTL-enabled containers before enabling the feature in production:
The editor directory provides tailored installation paths for VS Code, Cursor, Windsurf, VSCodium, Positron, Void, and Antigravity. Release v0.6.0 is available from both the Marketplace and GitHub Releases. The same VSIX supports compatible VS Code forks; Open VSX publication requires the devglobedev namespace and an OVSX_PAT repository secret.
Run the Publish editor extension workflow manually to validate and package one artifact, then select GitHub Release, Visual Studio Marketplace, or Open VSX destinations. Store publisher credentials only in the VSCE_PAT and OVSX_PAT GitHub Actions secrets.
Deploy the functions directory to an Azure Function App and configure these application settings for the 15-minute impact-history timer:
The timer resumes the current UTC day's capture in RU-bounded batches. Keep IMPACT_HISTORY_CONCURRENCY and IMPACT_HISTORY_BATCH_SIZE on the Container App because the Next.js endpoint performs the Cosmos work.
The Azure Functions app invokes the protected reminder endpoint daily at 14:00 UTC. The application sends reminders only to unverified contacts who consented to transactional email and have not received a reminder in the previous 72 hours; verified contacts stop receiving reminders immediately.
Configure these application settings on the Azure Function App:
Deploy the complete functions directory so each timer and its function.json are included.
DevGlobe is independently maintained and free to use. GitHub sponsorship helps fund Azure hosting and observability, public-data refreshes, GitHub API-backed processing, security updates, testing, and open-source maintenance.
Sponsorship never influences developer rankings, search placement, moderation, or access to private developer information. See the funding and transparency policy for tiers, benefits, costs, and current milestones.
Contributions are welcome! See CONTRIBUTING.md for setup instructions and areas where help is needed.
DevGlobe exposes a hosted Streamable HTTP MCP endpoint for public developer discovery and consent-gated agent introductions:
Public search and profile lookup work anonymously. Introduction requests and status polling require an issued agent credential. A local stdio connector remains available for clients that do not support remote MCP:
See docs/mcp-server.md for credential provisioning, Cosmos DB setup, client configuration, and the consent lifecycle. docs/agent-readiness.md documents machine-readable discovery, WebMCP, and the external DNS-AID deployment steps.
MIT — see LICENSE for details.
⭐ Star this repo if you find it useful!
Built with ❤️ by @sajeetharan
來源：README.md，提交 b1e58d3
Use when the user wants to find public developers by skill, name, language, location, agent availability, or active opportunity intent. Start discovery here; no authentication is required. Example: {"query":"TypeScript maintainers","location":"Germany","availableForAgents":true,"limit":5}.
limitquery必填languagelocationopportunityTypeavailableForAgentsUse when the user names a GitHub login or selects one DevGlobe search result and needs its public profile and contribution evidence. No authentication is required. Example: {"login":"sajeetharan"}.
login必填Use when the user wants alternatives similar to a known GitHub login. Similarity uses public repository, language, location, and profile signals and is not a suitability judgment. Example: {"login":"sajeetharan","limit":5}.
limitlogin必填Use when the user starts with a public GitHub repository and wants relevant indexed developers. Matches public owner, contribution, language, topic, repository, and self-declared opportunity signals; this is not a suitability judgment. Example: {"repository":"owner/repo","limit":10}.
limitrepository必填Use when recency or momentum matters. Lists public score gainers and high-ranking profiles new to impact tracking; do not use as a hiring recommendation. Example: {"days":30,"limit":10}.
dayslimitUse when the user wants one concrete open-source contribution opportunity for an indexed GitHub login. Read-only, rate limited, and does not reserve the issue. Example: {"login":"sajeetharan"}.
login必填Use only after the user explicitly asks to contact an opted-in developer. Requires a bearer token, creates a consent-gated pending request, and never returns private contact details. Example: {"developerLogin":"octocat","reason":"We would like help maintaining our open-source React library.","project":"Example UI"}.
reason必填project必填developerLogin必填Use after request_introduction to check a request created by the same authenticated agent. An accepted request returns only the public GitHub contact route.
id必填developerLogin必填已滿足適用檢查項的 100%
該評分衡量此收錄條目的完整程度，依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價，也不表示伺服器安全或目前可用：可連通性是帶日期的檢查結果，評分也不包含安裝量或使用者評價。
git clone https://github.com/sajeetharan/devglobe.gitcd devglobenpm installnpm run dev# Open http://localhost:3000npm run seed-emulatorCOSMOS_ENDPOINT=https://localhost:8081COSMOS_KEY=C2y6yDjf5/R+ob0N8A7Cgv30VRDJIWEHLM+4QDU5DE2nQ9nDuVTqobD4b8mGGyPMbIZnqyMsEcaGQy67XIw/Jw==npm run dev# .env.localCOSMOS_ENDPOINT=https://your-account.documents.azure.com:443/COSMOS_KEY=your-cosmos-keyAZURE_OPENAI_ENDPOINT=https://your-openai.openai.azure.com/AZURE_OPENAI_KEY=your-openai-keyEMBEDDING_DEPLOYMENT=text-embedding-3-smallAZURE_OPENAI_CHAT_DEPLOYMENT=gpt-4o-mininpm run devnpm run fetch-github # Fetch top devs from GitHub GraphQLnpm run fetch-stackoverflow # Enrich with StackOverflow reputationnpm run geocode # Convert locations to lat/lngnpm run build-data # Run full pipelinenpm run upload-cosmos # Upload to Azure Cosmos DB{ "login": "example", "specialTags": ["github-star", "microsoft-mvp", "aws-community-builder"]}npm run populate-special-tags # Dry runnpm run populate-special-tags -- --apply # Patch verified matches in Cosmos DB├── index.html # Entry HTML├── src/│ ├── main.jsx # Application bootstrap│ ├── App.jsx # Root component, data loading│ ├── components/│ │ ├── Globe.jsx # 3D globe (react-globe.gl)│ │ ├── Leaderboard.jsx # Ranked sidebar with filters│ │ ├── SearchBar.jsx # Hybrid/vector search input│ │ ├── DetailPanel.jsx # Developer detail card│ │ ├── Header.jsx # Top bar with branding│ │ └── LoadingOverlay.jsx # Loading state│ └── utils/│ ├── scoring.js # Composite scoring algorithm│ └── format.js # Number formatting helpers├── api/│ ├── developers.js # List all developers│ ├── developer.js # Single developer lookup│ └── search.js # Cosmos DB vector/hybrid search├── scripts/ # Data pipeline scripts├── styles/main.css # Dark theme styles└── data/ └── developers-sample.json # Sample data for local devnpm run setup-contacts-containernpm run activation-campaign -- --limit=100 --output=data/activation-campaign.jsonnpm run setup-activity-containerACTIVITY_INGEST_URL=https://your-site.example/api/activities/ingestACTIVITY_INGEST_SECRET=the-same-secret-configured-on-the-sitenpm run setup-live-presence-containernpm run setup-coding-stats-containerIMPACT_HISTORY_URL=https://www.devglobe.dev/api/cron/impact-historyCRON_SECRET=the-same-secret-configured-on-the-container-appEMAIL_VERIFICATION_REMINDERS_URL=https://www.devglobe.dev/api/cron/email-verification-remindersWEEKLY_DIGEST_URL=https://www.devglobe.dev/api/cron/weekly-digestCRON_SECRET=the-same-secret-configured-on-the-container-apphttps://www.devglobe.dev/mcpnpm run mcp