NestJS Observe
com.nestjsPublished by nestjs.comOfficial publisherv1.0.0Updated Oct 29, 2026
Production telemetry for NestJS apps: traces, errors, regressions, jobs and alerts.
Overview
Remote MCP endpoint for NestJS Observe that gives an assistant access to production telemetry from NestJS apps: traces, errors, regressions, jobs and alerts.
- What you can do
- Read production telemetry from NestJS applications: traces, errors, regressions, background jobs and alerts.
- No tool list is published, so the exact operations available to an assistant are not documented here.
- Access is through a hosted remote endpoint rather than a local package.
- When to use it
- Useful when you want an assistant to look into production behavior of NestJS applications — investigating errors, regressions, job failures or alerts — without leaving the chat, and you already use NestJS Observe.
- Requirements
- A remote MCP endpoint at observe-api.nestjs.com over streamable HTTP. OAuth authentication is required, so a NestJS Observe account with access to the relevant apps is needed. No environment variables or headers are declared.
Installation
In SourceWeft
- Open NestJS Observe in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.nestjs%2Fobserve/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"nestjs-observe": {
"type": "http",
"url": "https://observe-api.nestjs.com/mcp"
}
}
}Tools
0Version history
1- v1.0.0LatestOct 29, 2026
Score
83% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.
