DevGlobe

Name: DevGlobe
Author: sajeetharan

by sajeetharanversion 1.5.1i★ –iRuns in the cloud

Registry nameio.github.sajeetharan/devglobe

Install

Overview

Description from the maker (original English)

The open-source talent graph for humans and AI agents. Find developers.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs in the cloud
Transport: Streamable HTTP
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on the maker’s server: what you ask it goes through their server.
The registry lists no key to fill in.

You need

Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

Open Settings → Connectors
Press Add custom connector
Paste the address below and press Add
If it asks you to sign in, sign in with the maker

https://www.devglobe.dev/mcp

Run this in your terminal

claude mcp add --transport http devglobe https://www.devglobe.dev/mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "devglobe": {
      "url": "https://www.devglobe.dev/mcp"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "devglobe": {
      "type": "http",
      "url": "https://www.devglobe.dev/mcp"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

Open ChatGPT on the web → Settings → Connectors (Apps)
Press Create or Add (some plans need Developer mode under Advanced first)
Paste the address below, give it a name and save
If it asks you to sign in, sign in with the maker

https://www.devglobe.dev/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account sajeetharan, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
… Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
… Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Compared with others in Otheri

More stars than 0% of the other 32403 servers in this category
Published to the registry more recently than 32% of the other 32403 servers in this category
Basic checks equal to or better than 100% of the other 32403 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is DevGlobe safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.5.1) reached the registry 2 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, LickityClick

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday

Install

LickityClick

by lickity.click

Create, edit and track LickityClick short links, campaigns and click stats from your AI assistant.

Computer or cloudUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

🌐 DevGlobe

The open-source talent graph for humans and AI agents.

*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/mcp to 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.

🎬 Watch the DevGlobe Demo

DevGlobe: The Open-Source Talent Graph for Humans and AI Agents

✨ Features

Interactive 3D Globe — Explore developers pinned to their real-world locations using Three.js
AI-Powered Search — Hybrid + vector search via Azure Cosmos DB (e.g. "AI & deep learning", "full stack JS dev")
Composite Scoring — Each developer scored 0–100 across 6 dimensions
Leaderboard — Filter by country, language, or sort by score/stars/commits
Developer Profiles — Click any pin to see detailed stats, top repos, and contribution breakdown
Remote MCP Access — Agents can discover developers and request consent-gated introductions through hosted tools
VS Code Extension — Go live on the developer globe, build private coding stats, search developers, and configure MCP from the editor
Mobile Responsive — Bottom-sheet filters and full-width search on smaller screens

🚀 Quick Start

Option 1: Zero-config (sample data, no database needed)

git clone https://github.com/sajeetharan/devglobe.git

cd devglobe npm install npm run dev

Open http://localhost:3000

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).

Option 2: Cosmos DB Emulator (full database experience locally)

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:

   npm run seed-emulator

Create `.env.local` (the seed script prints this for you):

   COSMOS_ENDPOINT=https://localhost:8081

COSMOS_KEY=C2y6yDjf5/R+ob0N8A7Cgv30VRDJIWEHLM+4QDU5DE2nQ9nDuVTqobD4b8mGGyPMbIZnqyMsEcaGQy67XIw/Jw==

Run the app:

   npm run dev

The emulator key above is Microsoft's well-known emulator key — it is intentionally public and only works locally.

Option 3: Full Azure backend (vector + hybrid search)

For the complete experience including AI-powered search:

# .env.local

COSMOS_ENDPOINT=https://your-account.documents.azure.com:443/ COSMOS_KEY=your-cosmos-key AZURE_OPENAI_ENDPOINT=https://your-openai.openai.azure.com/ AZURE_OPENAI_KEY=your-openai-key EMBEDDING_DEPLOYMENT=text-embedding-3-small AZURE_OPENAI_CHAT_DEPLOYMENT=gpt-4o-mini

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.

npm run dev

🏗️ Tech Stack

Layer	Technology
Frontend	React 19, Three.js (react-globe.gl), Next.js 15
Search	Azure Cosmos DB (vector + hybrid search)
API	Next.js API Routes
Hosting	Azure Container Apps and Azure Functions
Data Pipeline	Node.js scripts (GitHub GraphQL, StackOverflow API, geocoding)

📊 Scoring Formula (0–100)

Dimension	Weight	Source
GitHub Stars	20%	Total stars across repos
GitHub Commits	20%	Yearly commit activity
Repo Reach	15%	Forks + watchers
SO Reputation	25%	StackOverflow reputation
SO Engagement	15%	Answer acceptance × count
Community	5%	Followers + badges

All dimensions are log-normalized to prevent outlier domination.

🔧 Building the Full Dataset

Requires API keys — copy .env.example to .env and fill in your tokens.

npm run fetch-github          # Fetch top devs from GitHub GraphQL

npm run fetch-stackoverflow # Enrich with StackOverflow reputation npm run geocode # Convert locations to lat/lng npm run build-data # Run full pipeline npm run upload-cosmos # Upload to Azure Cosmos DB

Developer credentials

Verified community credentials are stored explicitly on each developer document. Do not infer them from stars, followers, or profile text.

"login": "example", "specialTags": ["github-star", "microsoft-mvp", "aws-community-builder"] }

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:

npm run populate-special-tags             # Dry run

npm run populate-special-tags -- --apply # Patch verified matches in Cosmos DB

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.

📁 Project Structure

├── 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 dev

🌍 Deploy to Azure Container Apps

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:

Variable	Purpose
`COSMOS_ENDPOINT`	Azure Cosmos DB endpoint
`COSMOS_KEY`	Azure Cosmos DB key
`COSMOS_DATABASE`	Database name
`COSMOS_CONTAINER`	Container name
`COSMOS_ACTIVITY_CONTAINER`	Rolling GitHub activity container (`activities`)
`COSMOS_CONTACTS_CONTAINER`	Private lifecycle-email contact container (`developer-contacts`)
`COSMOS_ENGAGEMENT_CONTAINER`	Privacy-filtered engagement events (default: `engagement-events`)
`COSMOS_CONTRIBUTION_STATE_CONTAINER`	Shared GitHub recommendation quota state (default: `contribution-opportunity-state`)
`ENGAGEMENT_HASH_SECRET`	HMAC secret for session-window deduplication; defaults to `SESSION_SECRET`
`ACTIVITY_INGEST_SECRET`	Bearer secret for the activity collector endpoint
`RESEND_API_KEY`	Optional Resend API key for claim and approval emails
`EMAIL_FROM`	Sender on a domain verified by Resend
`COSMOS_WATCHLIST_CONTAINER`	Optional private watchlist container name (default: `watchlists`)
`COSMOS_IMPACT_HISTORY_CONTAINER`	Optional impact snapshot container name (default: `impact-history`)
`COSMOS_LIVE_PRESENCE_CONTAINER`	Opt-in live heartbeat container (default: `live-presence`)
`COSMOS_CODING_STATS_CONTAINER`	Private daily coding aggregates (default: `coding-stats`)
`CRON_SECRET`	Bearer token shared by protected cron endpoints and Azure Timer Functions
`EMAIL_PREFERENCE_SECRET`	HMAC secret for weekly-email unsubscribe links; defaults to `SESSION_SECRET`

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:

npm run setup-contacts-container

See the [lifecycle email PRD](docs/prd/lifecycle-email-not

Only the beginning is shown; read the rest in the repo

DevGlobe

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

LickityClick

README from the maker

🌐 DevGlobe

🎬 Watch the DevGlobe Demo

✨ Features

🚀 Quick Start

Option 1: Zero-config (sample data, no database needed)

Open http://localhost:3000

Option 2: Cosmos DB Emulator (full database experience locally)

Option 3: Full Azure backend (vector + hybrid search)

🏗️ Tech Stack

📊 Scoring Formula (0–100)

🔧 Building the Full Dataset

Developer credentials

📁 Project Structure

🌍 Deploy to Azure Container Apps