Imported from the official MCP registry - entry dev.appcontext/appcontext v0.1.0. Ratings and installs below are from this marketplace.
AppContext
Live iOS Simulator and browser screenshots, logs, and a personal MCP hub for AI coding agents.
Packages
npm: appcontext-mcp @ 0.1.0
Registry entry: dev.appcontext/appcontext
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
# after Install: the listing is in your workspace's routing pool - nothing else to configurecurl-s-X POST https://osr-api.kindrock-caaab1a2.centralindia.azurecontainerapps.io/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'# or pin it on the OpenAI-compatible endpoint: {"model": "mcp-dev-appcontext-appcontext", ...}
Manifest
An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.
mcp-dev-appcontext-appcontext.ocm.jsonjson
{
"ocm": "1",
"id": "mcp-dev-appcontext-appcontext",
"kind": "tool",
"name": "AppContext",
"description": "Live iOS Simulator and browser screenshots, logs, and a personal MCP hub for AI coding agents.",
"publisher": "dev.appcontext",
"version": "0.1.0",
"capabilities": {
"domains": [
"observability"
],
"tags": [
"mcp",
"mcp-server",
"npm",
"mcp-registry"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"Live iOS Simulator and browser screenshots, logs, and a personal MCP hub for AI coding agents."
],
"primary": false,
"metadata": {
"source": {
"provider": "mcp-registry",
"path": "server.json",
"ref": "0.1.0",
"url": "https://registry.modelcontextprotocol.io/v0/servers/dev.appcontext%2Fappcontext",
"key": "dev.appcontext/appcontext",
"registry": "https://registry.modelcontextprotocol.io"
}
}
}
Fetch it by URL: GET /api/v1/registry/mcp-dev-appcontext-appcontext/manifest?version=0.1.0
Reviews
Star ratings from people who tried it. One review per account; edit yours any time.
No reviews yet. Install it, try it, and be the first to rate it.
Installed into a catalogue, chosen by a router
Install AppContext and it becomes one more candidate the router can pick - when it fits.
A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.
Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.
Will this lock us into another vendor?
No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.
What happens when a provider fails?
The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.
Support assistant
Answers from the documentation; checking which model is on duty
Hi - I answer from the OpenSmartRoute documentation: routing, the API, plans and quotas, self-hosting. Ask away, or open a support ticket if you need a person.
Grounded in the docs - follow a source before acting on it.