Intended to integrate with Welcome to the Jungle recruitment workflows, providing read-only access to organization, job, candidate, and movement data. Note: the integration is not implemented yet.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@JungleBridge MCP What's your connection status?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Your Welcome to the Jungle recruitment workflows, in your AI assistant.
Development scaffold — the WTTJ integration is not implemented yet.
This repository provides a working local FastMCP STDIO server and a reproducible
Python development environment. Its only tool, get_connection_status, returns
not_implemented; it makes no API request and reads no credentials.
Open this repository in VS Code and choose Dev Containers: Reopen in Container.
Python, uv and Claude Code are included. Run claude inside the container to sign in.
Or install uv locally:
make bootstrap
make check
make audit
make build
uv run --no-sync junglebridge-mcpThe last command waits for a client speaking MCP over STDIO; it is not a chat CLI. See the French development guide, architecture, capability matrix and security notes.
Related MCP server: MCP Server Template
Read-only organization, job, candidate and movement tools, then bounded recruitment summaries. API access and scopes must be confirmed before a private pilot. No automated candidate ranking, hiring decisions, emails or job publication. No affiliation or partnership with Welcome to the Jungle is claimed.
Apache-2.0. Community is independent and intended for self-managed professional use. Optional proprietary enterprise extensions will live in a separate repository. No commercial Community quota is planned; upstream and technical limits will apply.
Return scaffold status only; does not verify or contact the WTTJ API.
Inputs: no named parameters. Returns: Static scaffold status, never an assertion of API connectivity.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 1 tool
With only a single tool, there is no possibility of confusion or overlap. The tool's purpose is clearly stated, albeit limited.
The single tool follows the snake_case verb_noun pattern (get_connection_status), which is consistent and predictable.
A server with only one trivial tool that merely returns a scaffold status without any real API interaction is an extreme mismatch for the apparent purpose of a JungleBridge MCP. It feels like a placeholder rather than a functional server.
The tool does not actually verify or contact the WTTJ API, and there are no other tools to cover any meaningful operations. The surface is severely incomplete and would cause agent failures.
Remote MCP server for supportsheep: run AI interviews and manage support content for your blog.
Remote MCP server for supportsheep: run AI interviews and manage support content for your blog.
MCP server that lets AI assistants use all OneSchema features exposed via the public API.
Nifty's MCP server — exposes tasks, projects, messages, and files as tools for AI agents.
