@crush-protocol/mcp-client 0.4.3 → 0.4.5
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/INSTRUCTIONS.md +16 -0
- package/README.md +46 -659
- package/dist/cli.js +6 -0
- package/dist/mcp/authPreflight.d.ts +9 -0
- package/dist/mcp/authPreflight.js +26 -0
- package/dist/mcp/oauthProvider.d.ts +2 -0
- package/dist/mcp/oauthProvider.js +8 -1
- package/dist/mcp/oauthRemoteClient.d.ts +3 -0
- package/dist/mcp/oauthRemoteClient.js +31 -18
- package/dist/mcp/proxy.js +29 -114
- package/dist/onboarding/cliOutput.d.ts +2 -0
- package/dist/onboarding/cliOutput.js +15 -0
- package/package.json +68 -46
- package/LICENSE +0 -21
- package/dist/__tests__/cliOutput.test.d.ts +0 -1
- package/dist/__tests__/cliOutput.test.js +0 -34
- package/dist/__tests__/e2e.test.d.ts +0 -1
- package/dist/__tests__/e2e.test.js +0 -50
- package/dist/__tests__/oauthProvider.test.d.ts +0 -1
- package/dist/__tests__/oauthProvider.test.js +0 -45
- package/dist/__tests__/oauthStorage.test.d.ts +0 -1
- package/dist/__tests__/oauthStorage.test.js +0 -52
package/INSTRUCTIONS.md
CHANGED
|
@@ -2,6 +2,22 @@
|
|
|
2
2
|
|
|
3
3
|
You have access to **Crush Protocol MCP**, an AI-native quantitative trading platform. Use these tools to help users research markets, build strategies, run backtests, and manage live trading.
|
|
4
4
|
|
|
5
|
+
Package identity:
|
|
6
|
+
|
|
7
|
+
- npm package: `@crush-protocol/mcp-client`
|
|
8
|
+
- product names users may mention: `Crush`, `Crush MCP`, `Crush Protocol MCP`
|
|
9
|
+
- server name in MCP host configs: `crush-protocol`
|
|
10
|
+
|
|
11
|
+
If a user mentions `@crush-protocol/mcp-client`, interpret that as the official hosted Crush MCP client.
|
|
12
|
+
|
|
13
|
+
Preferred onboarding sequence:
|
|
14
|
+
|
|
15
|
+
1. `npx -y @crush-protocol/mcp-client setup --cursor`
|
|
16
|
+
2. `npx -y @crush-protocol/mcp-client login`
|
|
17
|
+
3. If tools still fail, run:
|
|
18
|
+
- `npx -y @crush-protocol/mcp-client auth:status`
|
|
19
|
+
- `npx -y @crush-protocol/mcp-client doctor`
|
|
20
|
+
|
|
5
21
|
Authentication note: remote MCP requests use OAuth Bearer access tokens issued by the Crush OAuth server. In supported MCP hosts, users typically authenticate once with:
|
|
6
22
|
|
|
7
23
|
`npx -y @crush-protocol/mcp-client login`
|