Enhanced MCP server for Limitless Pendant with advanced conversation analysis, meeting detection, action item extraction, and comprehensive
R3f is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
Open InstallationWhat it does
MCP server that bridges AI tools to a running React Three Fiber scene
Quickstart
# 1 — run it from where its publisher ships it
npx -y r3f-mcp-server
# 2 — ask your agent something
> MCP server that bridges AI tools to a running React Three Fiber scene
R3f is free: there is no plan to choose, no cap to set and nothing that can bill you.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts R3f as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. It is scanned, signed and pinned to the version you choose — read the surface before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. Claude Code registers it in one command.
claude mcp add r3f-mcp -- npx -y r3f-mcp-serverReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
24 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Add a new object to the running R3F scene. Supports meshes with standard
Takes no parameters.
Save a live-injected preview component to an actual file in the user\
Takes no parameters.
Play, pause, stop, or seek an animation on a scene object.
Takes no parameters.
Generate a React Three Fiber component from a natural language description.
Takes no parameters.
List all active animations in the scene. Returns clip name, target object,
Takes no parameters.
Get detailed properties of a specific object in the scene by name or UUID.
Takes no parameters.
Get real-time performance metrics: FPS (averaged over last 60 frames), draw calls,
Takes no parameters.
Profile the scene for a specified duration and return statistics:
Takes no parameters.
Read the Rapier physics world state: rigid bodies, colliders, joints, velocities,
Takes no parameters.
List all currently active live-preview components in the running scene.
Takes no parameters.
Get the axis-aligned bounding box (AABB) of an object or group in world coordinates.
Takes no parameters.
Measure the world-space distance between two objects.
Takes no parameters.
List all objects currently visible within the camera\
Takes no parameters.
Remove a live-preview component from the running scene.
Takes no parameters.
Remove an object from the scene by name or UUID.
Takes no parameters.
Create an entire new R3F project from a natural language description.
Takes no parameters.
Compare the current scene to the last snapshot (taken by scene_graph or a previous scene_diff).
Takes no parameters.
Get the complete scene graph of the running R3F application.
Takes no parameters.
Capture a screenshot of the current rendered frame as a PNG image.
Takes no parameters.
Update material properties of a mesh in the scene.
Takes no parameters.
Update the position, rotation, or scale of an object in the scene.
Takes no parameters.
Show or hide an object in the scene.
Takes no parameters.
Inject R3F/Three.js component code into the running browser scene for immediate live preview.
Takes no parameters.
Get expert-level best practices, recipes, and API references for React Three Fiber.
Takes no parameters.
- Every tool, no call limit
- No card, no account needed
- Source published under a licence you can read
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because nothing bills
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable. R3f costs nothing to install and nothing to call, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | none | publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read | −2 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Pinned to 0.5.2 — the install command below asks for that release. A pin is part of an install, so it is kept for this visit and written down when you install.
No release note was published with this version.
Only accounts with at least 50 real tool calls against this server in the last 90 days can post. Ratings are weighted by how much the reviewer actually uses it, and publishers can reply once per review.
Writing one takes an account with at least 50 real tool calls against R3f in the last 90 days. That is the whole gate — there is no other way to post, which is why the counts beside each review are worth reading.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes an account with 50 real tool calls against it.