Watchlist tracking
Reviewed for relevance and future tracking value.
MCP100 Assessment
Watchlist / Tracking
Why we’re tracking it
Follow-up value is specific to Build-time MCP route generation from declarative Lovable tool definitions: Does manifest extraction remain separate from runtime tool counts while strict schemas reject undeclared arguments?
Reviewed · Documentation review; complete setup workflow not independently tested
Best fit
Building typed MCP endpoints inside Lovable/Vite applications
What we know
TypeScript SDK for declaring MCP tools, emitting application routes and optionally enforcing OAuth 2.1 resource-server auth.
Maintenance / activity evidence
- @lovable.dev/mcp-js 3.0.4 published 2026-09-25T09:09:47.142Z
Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.
Verification gaps / watch-outs
- Installation and comprehensive security have not been independently audited.
- Application handler authorization. Writes: Depends on authored tools.
- Optional JWT validation against configured issuer/JWKS.
- Sensitive access: Application/downstream API data
- Secure by configuration: omitted auth leaves endpoints unauthenticated, so authorization must be explicit.
Full authority, access and evidence limits are available in Review context and Access & risk.
Popularity
· 872k package downloads / 30 days
Downloads observed Sep 25, 2026.
30-day package downloads intentionally left null because the package-stats provider ran out of credits during Batch 3 QA.
30-day package downloads intentionally left null because the package-stats provider ran out of credits during Batch 3 QA.
All limitations / Review context
Does manifest extraction remain separate from runtime tool counts while strict schemas reject undeclared arguments?
The bounded review of the publisher's documented Build-time MCP route generation from declarative Lovable tool definitions and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.
- Secure by configuration: omitted auth leaves endpoints unauthenticated, so authorization must be explicit.
- Application handler authorization.
- Optional JWT validation against configured issuer/JWKS.
- Passes verified claims/token to app handlers.
- Reviewed write actions: Depends on authored tools
- Sensitive access: Application/downstream API data
- Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
- Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
- Documented tool authority and any remote data handling must be checked before installation or use.
- Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
- Repository identity/shared star metric
- Does not implement authorization server/consent flows.
- If auth is omitted, handlers are unauthenticated.
Original activity observations
- @lovable.dev/mcp-js 3.0.4 published 2026-09-25T09:09:47.142Z
Technical identity
npm/@lovable.dev/mcp-js- Exact implementation source
- https://www.npmjs.com/package/@lovable.dev/mcp-js ↗
- Reviewed resource type
- SDK
- Package identity
- @lovable.dev/mcp-js
- Service endpoint
- /mcp
Evidence & Sources
- Evidence basis
- Recorded source evidence
- Setup runtime verification
- Not independently runtime-tested by MCP100 for this setup workflow.
Reviewed · Latest source observation
- Package registry ↗
@lovable.dev/mcp-js
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.
Setup · Watchlist
SDK setup
Publisher instructions.
Source evidence observed .
Additional setup details required — see the specific gaps below.
Install SDK / application integration
Publisher instructionsDeveloper library/integration. Install in an application; not a plug-and-play MCP Server. Review publisher README. Not a standalone local MCP server; application integration required.
publisher documented install or connection · Publisher instructions
npm install @lovable.dev/mcp-jsConfigure / authenticate
MCP100 setup guideLovable MCP JS defines and hosts MCP routes inside an application. It is a framework/library, not a ready standalone endpoint.
Check connection
Suggested checkSDK: configure your own Lovable app MCP route and test authenticated MCP initialization/tools/list in an app test environment; not a standalone npx server. SDK/plugin validation means app import/initialization or feature availability, not an MCP client tools/list test unless the consuming app actually exposes a server.
Remove / uninstall / revoke
MCP100 setup guideRemove `@lovable.dev/mcp-js` from the host application with `npm uninstall @lovable.dev/mcp-js`, delete framework MCP route/middleware wiring, and redeploy. No standalone stdio server registration is implied.
MCP client unregister, stopping hosted processes, package uninstall, OAuth disconnect and token revocation are distinct actions.
A claude mcp remove command is only valid for Claude Code when the local registration actually has that name. Other MCP hosts require their own UI/config cleanup.
Separate credential guidance / limitations: @lovable.dev/mcp-js implements an MCP OAuth resource server and validates JWTs; it does not implement /authorize, /token, refresh, or consent. Revoke via the app-configured OAuth issuer (e.g. Supabase), not through this SDK.
Package / application cleanup · matching installation environment · MCP100 composed guide
npm uninstall @lovable.dev/mcp-js
Official Documentation & Sources
What it does
TypeScript SDK for declaring MCP tools, emitting application routes and optionally enforcing OAuth 2.1 resource-server auth.
- Capability
- Developer Tools
- Resource type
- SDK
- Industry
- Software & Technology
- Best fit
- Building typed MCP endpoints inside Lovable/Vite applications
Representative uses
- Define typed tools
- Expose Streamable HTTP routes
- Publish build-time manifests
- Protect endpoints with OAuth
Limitations
- Does not implement authorization server/consent flows.
- If auth is omitted, handlers are unauthenticated.
Reviewed access
Access & risk
Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.
- Authentication
- Optional JWT validation against configured issuer/JWKS.
- Permissions
- Application handler authorization.
- Data handling
- Passes verified claims/token to app handlers.
- Cost
- unknown
- Risk and cautions
- Secure by configuration: omitted auth leaves endpoints unauthenticated, so authorization must be explicit.
Access scope and cautions
- Write actions
- Depends on authored tools
- Sensitive access
- Application/downstream API data
- Risk level
- moderate
FAQ
Based on reviewed evidence as of 2026-10-06. Watchlist tracking is not a recommendation or a security certification.
Which tasks are documented for this implementation?
What setup and authentication are documented?
Can it modify data or perform write operations?
What data-handling boundary should I consider?
What limitations and risks should I check before use?
Is this an official MCP?
Lovable is listed as First-party MCP in MCP100’s current evidence.