@aventurevc/mcp-server 0.7.329 → 0.8.0

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 CHANGED
@@ -1,37 +1,105 @@
1
- # aventure-mcp
1
+ # aVenture MCP server
2
2
 
3
- Public aVenture Streamable HTTP MCP server. Most clients need no install: the
4
- [MCP quickstart](https://docs.aventure.vc/mcp) connects them to the hosted server
5
- at `https://mcp.aventure.vc/mcp`. Self-host with this package when your client
6
- cannot complete an OAuth flow.
3
+ Give an AI client access to aVenture's research data on companies, people, funding,
4
+ and news through the Model Context Protocol (MCP).
7
5
 
8
- Requires Node.js 24.18 or later in the 24.x series.
6
+ Most clients need no install: connect them to the hosted server at
7
+ `https://mcp.aventure.vc/mcp` and sign in with OAuth. Install this package only to
8
+ run the server yourself, for example when your client cannot complete an OAuth
9
+ sign-in. The [aVenture MCP quickstart](https://docs.aventure.vc/mcp) covers both
10
+ paths.
9
11
 
10
- ## Install and start
12
+ ## Connect to the hosted server
13
+
14
+ Configure your client with these settings:
15
+
16
+ - URL: `https://mcp.aventure.vc/mcp`
17
+ - Transport: Streamable HTTP
18
+ - OAuth client ID: `KL7mINzGk0le0QiD`
19
+ - Client secret: none; this is a public client
20
+
21
+ The client discovers the authorization server from the MCP URL and signs in with
22
+ authorization code and PKCE. Dynamic client registration is disabled, so enter the
23
+ client ID explicitly. A client that accepts only a URL fails with
24
+ `does not support dynamic client registration`.
25
+
26
+ For example, add the server to Claude Code for all your projects:
27
+
28
+ ```sh
29
+ claude mcp add --scope user --transport http \
30
+ --client-id KL7mINzGk0le0QiD --callback-port 6276 \
31
+ aventure https://mcp.aventure.vc/mcp
32
+ ```
33
+
34
+ Then run `/mcp` in Claude Code, select `aventure`, and complete browser sign-in.
35
+
36
+ The registered redirect URIs are:
37
+
38
+ - `http://127.0.0.1/callback`
39
+ - `http://localhost/callback`
40
+ - `https://chatgpt.com/connector_platform_oauth_redirect`
41
+ - `https://claude.ai/api/mcp/auth_callback`
42
+
43
+ A loopback redirect may use any available port, such as
44
+ `http://127.0.0.1:6276/callback`, as long as it keeps the `/callback` path.
45
+
46
+ To test the sign-in flow without a client, run the MCP Inspector in a terminal,
47
+ sign in to aVenture, and approve access. The Inspector lists the tools when sign-in
48
+ succeeds.
49
+
50
+ ```sh
51
+ npx @modelcontextprotocol/inspector@2.6.0 --cli \
52
+ --server-url https://mcp.aventure.vc/mcp \
53
+ --client-id KL7mINzGk0le0QiD \
54
+ --callback-url http://127.0.0.1:6276/callback \
55
+ --method tools/list
56
+ ```
57
+
58
+ ## Run the server yourself
59
+
60
+ The server requires Node.js 24.18 or later in the 24.x series. Installation fails
61
+ on any other major version.
11
62
 
12
63
  ```sh
13
64
  npm install --global @aventurevc/mcp-server --@aventurevc:registry=https://registry.npmjs.org/
14
- aventure-mcp-server --help
15
65
  aventure-mcp-server
16
66
  ```
17
67
 
18
- The server listens at `http://localhost:3333/mcp`. Leave it running while your
19
- MCP client connects. It starts without a static credential; each MCP request needs
20
- a user credential. This package uses Streamable HTTP, so configure a URL instead
21
- of a stdio command.
68
+ The `--@aventurevc:registry` flag makes npm install from the public npm registry
69
+ even when your npm configuration maps the `@aventurevc` scope somewhere else. The
70
+ package installs the same server under two command names, `aventure-mcp-server`
71
+ and `aventure-mcp`.
72
+
73
+ The server listens at `http://localhost:3333/mcp` and accepts connections from this
74
+ computer only. Keep it running while your client is connected. It speaks
75
+ Streamable HTTP, not stdio, so configure your client with a URL, not a command.
76
+
77
+ | Setting | What it changes |
78
+ | --- | --- |
79
+ | `AVENTURE_MCP_PORT` environment variable | Listening port (default `3333`) |
80
+ | `AVENTURE_MCP_PATH` environment variable | MCP route (default `/mcp`) |
81
+ | `AVENTURE_MCP_JSON_LIMIT` environment variable | Maximum request body size |
82
+ | `--host <address>` option | Network address to bind instead of `127.0.0.1`; `0.0.0.0` exposes the server to your network |
22
83
 
23
- ## Connect with a personal API key
84
+ Update the client URL when you change the port or route.
24
85
 
25
- Sign in, open [aventure.vc/settings/api-keys](https://aventure.vc/settings/api-keys),
26
- and choose **Add new key**. Store the key in your MCP client's secret storage.
27
- The HTTP request must carry `Authorization: Bearer <personal-api-key>`.
86
+ ### Authenticate with a personal API key
28
87
 
29
- For clients supporting `mcpServers` URL configuration:
88
+ A self-hosted server has no OAuth sign-in and no credential of its own. Every
89
+ request must carry a personal API key as a bearer token.
90
+
91
+ 1. Sign in to aVenture and create a key in
92
+ [aVenture API key settings](https://aventure.vc/settings/api-keys).
93
+ 2. Store the key in your MCP client's secret storage. Never commit it to a file.
94
+ 3. Configure the client to send `Authorization: Bearer <personal-api-key>`.
95
+
96
+ For clients that read an `mcpServers` configuration:
30
97
 
31
98
  ```json
32
99
  {
33
100
  "mcpServers": {
34
101
  "aventure": {
102
+ "type": "http",
35
103
  "url": "http://localhost:3333/mcp",
36
104
  "headers": {
37
105
  "Authorization": "Bearer <personal-api-key>"
@@ -41,53 +109,49 @@ For clients supporting `mcpServers` URL configuration:
41
109
  }
42
110
  ```
43
111
 
44
- Replace the placeholder through your client's credential configuration; its secret
45
- interpolation syntax may differ.
112
+ Replace `<personal-api-key>` using your client's secret interpolation syntax, which
113
+ differs between clients. A request without a key receives status `401`.
46
114
 
47
- ## Authenticate with native OAuth
115
+ ## Verify the connection
48
116
 
49
- Connect to the hosted server at `https://mcp.aventure.vc/mcp` with an
50
- OAuth-capable client. Configure the public client ID `KL7mINzGk0le0QiD`;
51
- no client secret is required. The client discovers the authorization server
52
- from the MCP endpoint and uses authorization code with PKCE. Dynamic client
53
- registration is disabled.
117
+ List the tools, call `aventure_status`, and then call `aventure_help`.
54
118
 
55
- The registered redirect URIs are:
119
+ | Tool | What it does |
120
+ | --- | --- |
121
+ | `aventure_status` | Returns API status, host, and the access your credential carries |
122
+ | `aventure_help` | Finds the operation for a task and lists the inputs it needs |
123
+ | `aventure_search` | Runs a search operation over companies, people, news, or content |
124
+ | `aventure_lookup` | Resolves a name, URL, domain, slug, or other identifier to a record |
125
+ | `aventure_read` | Reads one record or the records attached to it |
56
126
 
57
- - `http://127.0.0.1/callback`
58
- - `http://localhost/callback`
59
- - `https://chatgpt.com/connector_platform_oauth_redirect`
60
- - `https://claude.ai/api/mcp/auth_callback`
127
+ Accounts with write permission also see `aventure_write` and `aventure_delete`,
128
+ which change shared data immediately. The tool list reflects the signed-in
129
+ account's permissions, and the API checks permission again on every call.
61
130
 
62
- Loopback redirects may use an available port, such as
63
- `http://127.0.0.1:6276/callback`; keep the `/callback` path. A client using
64
- another callback path needs its own registered OAuth application.
131
+ ## Plans and usage
65
132
 
66
- For example, MCP Inspector 2.6.0 supports these settings:
133
+ Calls count toward your aVenture plan's usage. Some operations, such as
134
+ plain-English search, need a plan that includes them; without one, the API
135
+ responds with status `402`.
67
136
 
68
- ```sh
69
- npx @modelcontextprotocol/inspector@2.6.0 --cli \
70
- --server-url https://mcp.aventure.vc/mcp \
71
- --client-id KL7mINzGk0le0QiD \
72
- --callback-url http://127.0.0.1:6276/callback \
73
- --method tools/list
74
- ```
137
+ - Compare plans on the [aVenture pricing page](https://aventure.vc/pricing).
138
+ - Check your plan and current usage in
139
+ [aVenture subscription settings](https://aventure.vc/settings/subscription).
75
140
 
76
- Run it in an interactive terminal, sign in to aVenture, and approve access.
77
- The Inspector exchanges the authorization code and lists the MCP tools.
141
+ ## Diagnostics
78
142
 
79
- ## Verify access
143
+ The server writes diagnostics to standard error. It sends no logs, metrics, or
144
+ error reports to aVenture.
80
145
 
81
- Connect the client, list its tools, and call `aventure_status`, then `aventure_help`.
82
- The tool list reflects the permissions granted to the signed-in user. The API checks
83
- permission again when an operation runs.
146
+ ## Documentation
84
147
 
85
- Set `AVENTURE_MCP_PORT` or `AVENTURE_MCP_PATH` to change the listener and update
86
- the client URL to match.
148
+ - [MCP quickstart](https://docs.aventure.vc/mcp)
149
+ - [Authentication guide](https://docs.aventure.vc/authentication)
150
+ - [Error reference](https://docs.aventure.vc/errors)
151
+ - [API reference](https://docs.aventure.vc/api-reference)
87
152
 
88
- ## Diagnostics
153
+ The tool catalog is generated from the public aVenture OpenAPI specification.
89
154
 
90
- The public package writes diagnostics to stderr. OTLP logs, Prometheus metrics,
91
- and Sentry reporting are disabled.
155
+ ## License
92
156
 
93
- The tool catalog is generated from the public aVenture OpenAPI spec.
157
+ Apache License 2.0. See the [LICENSE file](LICENSE).