mcp

This MCP server package (@osaas/mcp-server) is deprecated. The functionality has been replaced by a remote Custom Connector that uses streamable HTTP with OAuth. There is no local MCP server to run for normal operation; instead, you should connect to the MCP endpoint provided by osaass.io/mcp. If you still need to explore locally, you can invoke the package via npx to quickly spin up a temporary instance, but be aware that it is no longer maintained and may not support current features or security requirements. The primary workflow now is to authenticate with OAuth and use the remote MCP endpoint to manage and process your MCP streams.

Prerequisites:

• Node.js and npm installed (recommended to use npx without installation).

Recommended approach (no local installation):

1. Ensure you have Node.js installed. If not, install from https://nodejs.org
2. Use the MCP server package via npx (no local installation required):

Code:

• npx -y @osaas/mcp-server

Optional (if you must install locally, though this is not advised for this deprecated package):

1. Initialize a project folder mkdir mcp-server && cd mcp-server
2. Install the package npm install @osaas/mcp-server
3. Run the server (if the package exposes a CLI entry point, e.g., node server.js or similar as documented in the package)

Note: The repository states that the MCP server is deprecated and the official guidance directs users to the remote Custom Connector. Prefer the remote endpoint for production usage.

-deprecated: This MCP server is no longer maintained. Use the remote Custom Connector at https://www.osaas.io/mcp with OAuth for authentication. -If you rely on this package for experimentation, be aware of potential incompatibilities with newer MCP specs or security requirements. -There is no officially supported local configuration beyond the legacy package usage via npx. -Environment variables and runtime options are not documented in the current repository; refer to the remote endpoint documentation for configuration details.