Centroid

Created By
NeuclaiLabsa year ago
A platform for managing your local MCP servers
Overview

What is OpenAstra?

OpenAstra is a chat-based open-source development platform designed for API discovery and testing, combining the functionalities of traditional API tools with the conversational capabilities of AI.

How to use OpenAstra?

To use OpenAstra, you can run it using Docker. After setting up, access the web interface at http://localhost:3000 and the backend OpenAPI documentation at http://localhost:8000/docs.

Key features of OpenAstra?

  • 💬 Chat with API Collections: Import and interact with APIs through natural conversation, supporting OpenAPI/Swagger specifications and Postman collections.
  • 🚀 Execute API Endpoints: Test and run API endpoints directly from the chat interface with real-time response data.
  • 🤖 Flexible LLM Support: Works with any OpenAI-compatible API, allowing for various models and configurable settings.

Use cases of OpenAstra?

  1. Simplifying API testing and interaction through conversational interfaces.
  2. Facilitating API documentation and exploration for developers.
  3. Enhancing productivity in API development workflows.

FAQ from OpenAstra?

  • Can OpenAstra work with any API?

Yes! OpenAstra supports any API that adheres to OpenAPI specifications.

  • Is OpenAstra free to use?

Yes! OpenAstra is open-source and free for everyone.

  • How can I contribute to OpenAstra?

You can contribute by cloning the repository, making changes, and submitting a pull request.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
NeuclaiLabs
Star
50
Language
TypeScript
License
Apache-2.0 license
Tags

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago