MCP Hive App
This is a Next.js project bootstrapped with create-next-app.
Getting Started
First, run the development server:
npm run dev
# or
yarn dev
# or
pnpm dev
# or
bun dev
Open http://localhost:3000 with your browser to see the result.
You can start editing the page by modifying app/page.tsx. The page auto-updates as you edit the file.
This project uses next/font to automatically optimize and load Geist, a new font family for Vercel.
Learn More
To learn more about Next.js, take a look at the following resources:
- Next.js Documentation - learn about Next.js features and API.
- Learn Next.js - an interactive Next.js tutorial.
You can check out the Next.js GitHub repository - your feedback and contributions are welcome!
Deploy on Vercel
The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.
Check out our Next.js deployment documentation for more details.
-
Experiment (Done)
- Check if auth settings can be passed during tool invocation - Done
- What should be the format of the auth settings? - Let client follow the format of the security scheme
- Do we need to pass the entire security scheme or passing api key is enough? - Let client follow the format of the security scheme
- What should be the format of the auth settings? - Let client follow the format of the security scheme
- Check if host can be passed during tool invocation - Done
- Check if auth settings can be passed during tool invocation - Done
Note:
-
list_tools
-
get_security_schemes
-
_request_timeout
-
_request_auth
-
_content_type
-
_headers
-
_host_index
Conclusion:
- We will provide a dedicated client
-
MCP Client
- Remove unnecessary input params from tools before passing to LLM like request auth, headers, etc. Openapi client generator add these params to each tool.
- Ensure client can read env variables and pass host and api key to the tools
-
MCP Server
- Setup CI/CD pipeline (Use codebuild, s3, ECR and ECS)
- Build docker image
- Host docker images on public ECR
- Deploy server on ECS
- Setup CI/CD pipeline (Use codebuild, s3, ECR and ECS)
-
Backend
- Maintain template for connection details
- Add an endpoint to generate connection details for a given hive
-
UI
- Update connection details. Local (docker) and Remote (Endpoint + Dedicated client)
Metadata
Release files for mcp-hive-cli 0.1.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| mcp_hive_cli-0.1.4.tar.gz | 4.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mcp_hive_cli-0.1.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 8.6 kB
Release files / mcp_hive_cli-0.1.4.tar.gz
| Download URL | mcp_hive_cli-0.1.4.tar.gz |
|---|---|
| Size | 4.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0aceb0dc74b585d5e70e4d5d4a63a19f3d9f19e1f2133965224f1ef77d927e00
|
|
BLAKE2b-256 checksum How to use checksums |
483dfe8a33e732e7ec005d0a69bfb71cbcc9409bada34a071d4c1e5a6ecf13ae
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.1 CPython/3.13.1
|
Release files / mcp_hive_cli-0.1.4-py3-none-any.whl
| Download URL | mcp_hive_cli-0.1.4-py3-none-any.whl |
|---|---|
| Size | 4.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
746405804db56ae804f4371a09b1711415ad556553294a7c3a7e479a3feddd4d
|
|
BLAKE2b-256 checksum How to use checksums |
0a74be9013e52cc203148cbe9e6b216f935e2d423e49bdece4c8a7f01367a7c0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.1 CPython/3.13.1
|
Security for mcp-hive-cli 0.1.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.