# Coder Legion Developers AI Agent Connect

> Coder Legion Developers MCP gives your AI agent direct read access to the Coder Legion public directory. You can search for engineers by skill, location, or experience, browse the full roster, and pull detailed individual profiles. It works with any MCP-compatible client like Claude, Cursor, or Windsurf, and requires no account or API key to start pulling data.

## Overview
- **Category:** developer-tools
- **Price:** Free
- **Endpoint:** https://edge.vinkius.com/vk_preview_nC77T1g4jojcGiHGUjg5tVC4y3odopdciRk9XVmT/ai-agent-connect
- **Tags:** coder-legion, developer-directory, developer-profiles, talent, recruiting, keyless

## Description

You can now give your AI agent a window into the Coder Legion community. This MCP lets your agent navigate the public directory of engineers, pulling specific data points like skill tags, location, experience levels, and community stats. Instead of manually clicking through web pages, you can simply ask your agent to find specific talent or survey the landscape of available developers. 

If you need to find a specialist, your agent can filter the community by combining name, skill, location, and minimum years of experience. Once you find a candidate that looks right, your agent can pull their entire public profile, including their headline, website, community roles, and detailed about text. It is a fast way to map out technical talent or find collaborators without the friction of manual searching. Since the directory is public, you don't need to manage any credentials or API keys; you just connect the MCP and start asking questions.

## Tools

### get_developer_profile
This tool pulls a single developer's complete public profile using their handle. It returns everything from their verified status and community roles to their specific skills and about text.

### list_developers
This tool lets your agent walk through the public directory in pages of 18 profiles. It provides names, headlines, locations, and experience levels for everyone in the roster.

### search_developers
This tool searches the community using up to four filters like name, skill, location, or minimum years of experience. All filters combine with an AND logic to narrow down results.

## Prompt Examples

**Prompt:** 
```
Find Coder Legion developers with at least 5 years of experience who list prompt engineering as a skill.
```

**Response:** 
```
I found several developers matching those criteria. The results include their names, verified status, and locations. Would you like me to pull the full profile for any of them?
```

**Prompt:** 
```
Show me the next page of the Coder Legion developer directory.
```

**Response:** 
```
Here are the next 18 profiles from the directory, including their headlines and skill tags. I can keep paging through or help you filter this list.
```

**Prompt:** 
```
Open the Coder Legion profile of the first developer found in a search for Kubernetes skills and summarize their stats.
```

**Response:** 
```
I've pulled that profile. The developer is verified, holds specific community roles, and has a significant number of followers. Their headline and about text are also available for review.
```

## Capabilities

### Filtered Talent Discovery
Your agent uses search filters to find engineers by specific technical skills or locations.

### Directory Browsing
Your agent can paginate through the entire community roster to survey available talent.

### Deep Profile Inspection
Your agent pulls full biographical and statistical data for individual developers.

### Zero-Config Access
Your agent accesses public data without needing you to provide an API key or account.

## Use Cases

### Technical Sourcing
Ask your agent to find all developers in a specific city with at least 3 years of Python experience.

### Competitor/Peer Mapping
Use the directory to identify the most active community members in a specific technology niche.

### Vetting Collaborators
Have your agent pull full profiles to check a developer's community standing and verified status.

### Talent Auditing
Survey the entire directory to understand the distribution of skills across the community.

## Benefits

- Eliminates manual searching by letting your agent handle directory navigation.
- Removes the need to manage API keys or developer accounts.
- Provides structured data that your agent can immediately process and summarize.
- Allows for complex multi-filter searches through natural language.

## How It Works

Connecting to the Coder Legion directory is a direct process that requires no manual setup.

1. Connect the MCP to your preferred AI client via Vinkius.
2. Ask your agent to search or list developers using natural language.
3. The agent calls the appropriate tool to query the public directory.
4. The agent receives structured profile data and presents it to you.

## Frequently Asked Questions

**Do I need an API key to use this MCP?**
No. The Coder Legion directory is public, so this MCP works without any credentials or API keys.

**How many profiles can the agent see at once?**
The list tool returns profiles in batches of 18 using offset pagination.

**Can I filter by multiple criteria?**
Yes. You can combine name, skill, location, and minimum years of experience. These filters work together using AND logic.

**What kind of data can my agent retrieve from a profile?**
Your agent can get a developer's headline, location, website, community roles, stats like followers and points, and their full about text.

**Which AI clients can I use with this?**
You can use this with any MCP-compatible client, including Claude, Cursor, Windsurf, and VS Code.

**Do I need an account or API key?**
No. The Coder Legion developer directory and developer profile pages are public, so this connection is keyless — subscribe and use it. The separate Coder Legion connection covers the authenticated API surface (posts, jobs, series, groups, tags), which is where an API key is needed.

**What data does a directory record include?**
Each record has the developer's name, verified badge status, headline, location, years of experience, skill tags and the URL of their public profile. The profile tool adds community roles (with descriptions), website, join date, stats (points, badges, connections, followers, following), the full skill list and the about text.

**How does search work, and what if a search returns nothing?**
Filters combine with AND: name (partial match), a skill tag, a location, and a minimum years of experience (the directory supports 1, 3, 5 or 10). Results are paged by offset in groups of 18. When a combination comes back empty, drop the narrowest filter (usually the skill or the location) and retry — the tool tells the agent exactly that.

**What happens if I pass a handle that does not exist?**
The tool returns a clear "profile not found" error that points back at the directory tools, so the agent recovers by listing or searching first and then opening one of the returned profile URLs. Transient page-load failures surface as a retryable error instead of a crash.
