@apono-io/apono-mcp 0.2.51 → 0.2.52-beta.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +72 -0
- package/package.json +1 -1
package/README.md
ADDED
|
@@ -0,0 +1,72 @@
|
|
|
1
|
+
# Apono MCP
|
|
2
|
+
|
|
3
|
+
Just-in-time access to your infrastructure and SaaS tools for AI agents, governed by [Apono](https://www.apono.io/).
|
|
4
|
+
|
|
5
|
+
`@apono-io/apono-mcp` runs the Apono Agentic Gateway: a local MCP server for Claude Code, Cursor and Claude Desktop. The agent asks the gateway for what it needs. Apono grants scoped, time-limited access through your existing access flows, the gateway enforces your trust policies on every tool call, and every call is audited.
|
|
6
|
+
|
|
7
|
+
- **No standing credentials.** The agent never holds a long-lived secret. Apono issues credentials per request and revokes them when access expires.
|
|
8
|
+
- **Trust policies on every call.** Each tool call is classified by intent (read, write, delete, ...) and allowed, denied, or sent to a human for approval.
|
|
9
|
+
- **One server, many targets.** Databases, cloud accounts, Kubernetes and SaaS tools that your Apono admin connected, all behind one MCP server.
|
|
10
|
+
|
|
11
|
+
## Requirements
|
|
12
|
+
|
|
13
|
+
- Node.js 16 or later, for `npx`.
|
|
14
|
+
- An Apono account. Ask your Apono admin to enable Agentic access for you.
|
|
15
|
+
|
|
16
|
+
## Setup
|
|
17
|
+
|
|
18
|
+
### 1. Log in to Apono
|
|
19
|
+
|
|
20
|
+
```shell
|
|
21
|
+
npx -y @apono-io/apono-mcp@latest login
|
|
22
|
+
```
|
|
23
|
+
|
|
24
|
+
This opens your browser to sign in. You log in once per machine; the gateway refreshes the session on its own.
|
|
25
|
+
|
|
26
|
+
### 2. Add the gateway to your agent
|
|
27
|
+
|
|
28
|
+
**Claude Code**
|
|
29
|
+
|
|
30
|
+
```shell
|
|
31
|
+
claude mcp add apono -- npx -y @apono-io/apono-mcp@latest --agent-type claude-code
|
|
32
|
+
```
|
|
33
|
+
|
|
34
|
+
**Cursor** (`~/.cursor/mcp.json`)
|
|
35
|
+
|
|
36
|
+
```json
|
|
37
|
+
{
|
|
38
|
+
"mcpServers": {
|
|
39
|
+
"apono": {
|
|
40
|
+
"command": "npx",
|
|
41
|
+
"args": ["-y", "@apono-io/apono-mcp@latest", "--agent-type", "cursor"]
|
|
42
|
+
}
|
|
43
|
+
}
|
|
44
|
+
}
|
|
45
|
+
```
|
|
46
|
+
|
|
47
|
+
**Claude Desktop** (`claude_desktop_config.json`)
|
|
48
|
+
|
|
49
|
+
```json
|
|
50
|
+
{
|
|
51
|
+
"mcpServers": {
|
|
52
|
+
"apono": {
|
|
53
|
+
"command": "npx",
|
|
54
|
+
"args": ["-y", "@apono-io/apono-mcp@latest", "--agent-type", "claude-desktop"]
|
|
55
|
+
}
|
|
56
|
+
}
|
|
57
|
+
}
|
|
58
|
+
```
|
|
59
|
+
|
|
60
|
+
Restart the agent after you change its configuration.
|
|
61
|
+
|
|
62
|
+
### 3. Ask for what you need
|
|
63
|
+
|
|
64
|
+
Ask the agent in plain words, for example "query the orders table in the staging database". The agent finds the resource through Apono, requests access, and runs the call once access is granted. When a call needs approval, the approver gets a request and the agent waits for the decision.
|
|
65
|
+
|
|
66
|
+
## Versions
|
|
67
|
+
|
|
68
|
+
`@latest` always runs the newest stable gateway. To pin a version, name it instead, for example `@apono-io/apono-mcp@0.2.51`. On first run the package downloads the matching gateway binary to `~/.local/bin`, and later runs reuse it.
|
|
69
|
+
|
|
70
|
+
## Support
|
|
71
|
+
|
|
72
|
+
Contact your Apono admin, or reach Apono support at [support@apono.io](mailto:support@apono.io).
|