Loading…
The agent already knows your repository. Give it a scoped key and it sets up monitoring, keeps it in sync, triages the inbox, and answers “what is going on with my dependencies right now”. You keep the permissions, the destinations and the decisions.
Create a key under Connect an agent in the app. Name it after the machine or agent that will use it and keep the default scopes. The key is shown once.
Claude Code connects to the MCP server with a single command; any other MCP client takes the same address and header. If your agent speaks plain HTTP, the REST API has the same surface.
claude mcp add --transport http changelog-observer \ https://api.changelog.observer/mcp \ --header "Authorization: Bearer <key>"
Then say
Set up changelog.observer for this repo.
Or, over HTTP
curl -H "Authorization: Bearer <key>" \ https://api.changelog.observer/v1/projects
Read the manifests, map packages and config files to the vendor catalogue, create the project, register the sources, and report back what needs a human.
Send the current inventory again after a manifest change. The service reports what it added and kept, and proposes removals it never applies on its own.
Explain what arrived, propose sender rules, resolve review items, and ask you before trusting a sender.
List what is open for you, record investigating, affected or cleared with evidence, snooze a dependency, and push an incident to a ticket when you ask.
Suggest alert rules and preferences from what the record supports; apply them only with a key that has the right scope.
Source coverage, lag, delivery success and signal quality, with the definition of each number, so the report says what the dashboard says.
destinations:write scope, which you add on purpose.Four published skills package the workflows, so the agent does not improvise.
Set up monitoring for a repository or an area of it; re-sync after manifests change.
Triage what arrived at a project’s address: confirmations, unknown and unverified senders, sender rules.
Inspect or propose alert rules, check why something did or did not alert, retry deliveries.
Answer “what is going on with my dependencies right now”, record your side of incidents, hand one to a ticket.
Every write through the API lands in the audit log with the key that made it, the target and the change. Keys are hashed at rest, shown once, and can be revoked at any time. A key can be scoped to one project. A workspace owner’s key can hold workspace:admin for inviting and removing members; a project-scoped key never can.
Sign in, create a scoped key, and ask.