uefnmcp-connector
A local MCP server that grounds your AI assistant in the hosted Verse Cortex knowledge base — Epic's full UEFN documentation plus the Verse API index — through the metered verseisland.com gateway.
Plug it into Claude Desktop, Cursor, or Claude Code with your API key and your AI can now answer UEFN / Verse questions from real, current Epic docs and the indexed Verse API instead of guessing from stale training data. The KB grounding is the whole point: local models are routinely wrong about Verse syntax and API names — these tools fix that.
Tools it exposes
| MCP tool | What it does | Gateway tool |
|---|---|---|
verse_kb_search |
Semantic search over Epic UEFN docs + the Verse API | search_verse_kb |
verse_api_search |
Look up a Verse/Fortnite API symbol by name | search_verse_api |
verse_symbol |
Full signature + doc-comment for one symbol | get_verse_symbol |
verse_health |
Gateway / backend health probe | health_check |
Each call goes through the metered gateway: it authenticates your key, enforces your tier's daily limits, meters usage, and returns ranked KB results. The connector never touches the vector DB or the embedding server directly.
Install
pip install uefnmcp-connector
or run it without installing, straight from PyPI, via uvx:
uvx uefnmcp-connector # one-off run, no install
Get an API key
- Sign in at https://verseisland.com (Discord or email — free during beta).
- Go to https://verseisland.com/me/api-keys.
- Click Create key, copy the
uefn_sk_...value — it's shown once.
Configure your MCP client
The connector reads two environment variables:
| Variable | Default | Required |
|---|---|---|
VERSEISLAND_API_KEY |
– | yes (for KB tools) |
VERSEISLAND_GATEWAY_URL |
https://verseisland.com/mcp-api |
no |
VERSEISLAND_TIMEOUT |
30 (seconds) |
no |
Claude Code (CLI)
One paste:
claude mcp add uefnmcp \
--env VERSEISLAND_API_KEY=uefn_sk_your_key_here \
-- uefnmcp-connector
Claude Desktop
Edit claude_desktop_config.json (macOS:
~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\):
{
"mcpServers": {
"uefnmcp": {
"command": "uefnmcp-connector",
"env": {
"VERSEISLAND_API_KEY": "uefn_sk_your_key_here"
}
}
}
}
If uefnmcp-connector isn't on your PATH, use the module form:
"command": "python", "args": ["-m", "uefnmcp_connector"] (or
"command": "uvx", "args": ["uefnmcp-connector"]).
Cursor
Add to ~/.cursor/mcp.json (or .cursor/mcp.json in a project):
{
"mcpServers": {
"uefnmcp": {
"command": "uefnmcp-connector",
"env": {
"VERSEISLAND_API_KEY": "uefn_sk_your_key_here"
}
}
}
}
Restart the client. Ask it something like "search the Verse KB for how to spawn
a prop" and it will call verse_kb_search.
Tiers
Free during the beta-launch window (all tiers unlocked, no card). Beta signups lock the founder rate for 12 months.
| Tier | Price | verse_kb_search / verse_api_search |
verse_symbol |
|---|---|---|---|
| Free | $0 | 200 / day | 100 / day |
| Pro | $19/mo (founder $12) | 2,000 / day | 1,000 / day |
| Studio | $59/mo (founder $39) | unlimited | unlimited |
verse_health is always unlimited. Premium compile/build credit tools
(compile_verse, compile_and_fix, …) land in a later release behind the same
gateway. Manage keys and see usage at https://verseisland.com/me/api-keys.
Composing with uefn-mcp (local UEFN drive)
This connector is the KB-grounding half. To also drive UEFN — compile
Verse, build, place actors on your own machine — pair it with a local
UEFN driver server (uefn-mcp, distributed separately), which talks to your
local UEFN build setup over Node. Add both servers to your client:
{
"mcpServers": {
"uefnmcp": {
"command": "uefnmcp-connector",
"env": { "VERSEISLAND_API_KEY": "uefn_sk_..." }
},
"uefn-mcp": {
"command": "node",
"args": ["/path/to/uefn-mcp/dist/index.js"]
}
}
}
Your AI then grounds its Verse in the hosted KB (verse_* tools here) and
compiles/runs it locally (uefn-mcp tools) — the full write → ground → compile
loop, with the cloud KB doing the heavy lifting and your machine doing the
build. (Hosted compile credits via the gateway are on the roadmap; until then,
compile stays local via uefn-mcp.)
Development / local testing
pip install -e .
# Point at a local gateway instead of prod:
VERSEISLAND_GATEWAY_URL=http://localhost:3101/mcp-api \
VERSEISLAND_API_KEY=uefn_sk_... \
uefnmcp-connector # serves MCP over stdio
A standalone smoke test (no MCP client needed) lives in smoke_test.py.
License
Apache-2.0.
Metadata
Release files for uefnmcp-connector 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| uefnmcp_connector-0.1.1.tar.gz | 7.3 kB | Without provenance | Details for uefnmcp_connector-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| uefnmcp_connector-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for uefnmcp_connector-0.1.1-py3-none-any.whl |
Total release size: 15.8 kB
Release files / uefnmcp_connector-0.1.1.tar.gz
| Download URL | uefnmcp_connector-0.1.1.tar.gz |
|---|---|
| Size | 7.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7af369a508e20780199ea1b2eb35da6358b319a1aeab2693e67d2cad2665ea18
|
|
BLAKE2b-256 checksum How to use checksums |
e2f756ce8e4e738c144379aeb329301c6777b82609661b473c75806169d9c7e5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / uefnmcp_connector-0.1.1-py3-none-any.whl
| Download URL | uefnmcp_connector-0.1.1-py3-none-any.whl |
|---|---|
| Size | 8.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
284386bf606005a3cbad38d2f031851a463a3970e15e611aa67c931385448aef
|
|
BLAKE2b-256 checksum How to use checksums |
ea8adaf78726c4ddfb2e7f94204e23c1b7b39fdda62b7eb64a72ea6840af3bef
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for uefnmcp-connector 0.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.