Skip to content ReleaseVezual Beta is in the Plugins Console

Integrations

Your tools. Your code.
Connected to your data.

Bring your database workspace, application language and AI tools to OriginChainDB. Choose the connection that fits what you want to build.

Built to connect Three entry points
Database toolsPostgreSQL listener
Your applicationSDKs & HTTP
AI toolsMCP server
ONE MULTIMODAL DATABASEOriginChainDB
SQLVectorGraphFull-text
Choose an interface. Use its supported operations and access controls.

Database tools

Keep the workspace
you know.

Open your data in pgAdmin or DBeaver, or connect your application through a compatible driver.

01 Database workspace

pgAdmin

Use Query Tool to explore records and run supported SQL through your instance’s PostgreSQL listener.

Connection guide
02 Database workspace

DBeaver

Connect with the PostgreSQL driver, browse a known table and query your data from a familiar editor.

Connection guide
03 Application code

Drivers & ORMs

Use the current read-only PostgreSQL login for compatible queries. Send writes and schema changes through the HTTPS API.

Review compatibility
Dedicated instances

SQL clients and ORMs require an enabled PostgreSQL listener. The current login is read-only. Copy its host, port, credentials and TLS settings from Connect. Free and pooled configurations use the HTTPS API.

Connect first. Then test your workflow. Protocol support does not guarantee every PostgreSQL extension, administration tool or ORM migration will work.

Check supported behavior

SDKs & APIs

Build in your language.

Connect over HTTPS with an OriginChainDB client. Work with records, queries and search operations from your application code.

Eight SDKs are available on GitHub. Follow the installation steps for the version in your language guide and check its API coverage.

View all eight languages

Need the direct interface?

Use the HTTP reference for endpoints not wrapped by your client, or when building your own integration.

Browse API operations

MCP integration

Give your AI tools
database context.

The earlier OriginChainDB MCP integration connects a compatible AI client to tools for schema discovery, SQL, natural-language questions and search.

A local stdio server carries tool requests to your database’s HTTPS endpoint. Your configured credentials and the database determine which operations can run.

The server for the new access-token connection is not yet a verified public install. Confirm availability and client setup before connecting your instance.

Tool directorystdio
  • oc_list_schemas

    Inspect tables and their structure

  • oc_sql

    Run supported SQL

  • oc_ask

    Ask questions about your tables

  • oc_vector_topk

    Retrieve similar vectors

  • oc_fts_search

    Search indexed text

Ask and search tools require the corresponding instance capabilities.

Make the first connection

A clear path
from setup to your app.

Verify one small request, then test the operations your application will use.

01

Choose the interface

Use HTTPS for SDK and API requests, or the dedicated listener for supported PostgreSQL clients.

Connection settings
02

Scope the credentials

Use the credentials for your chosen interface. Keep secrets in your server environment and verify the intended access.

Authentication & access
03

Test the real workload

Check reads, authorized writes and expected failures. Review transaction and retry behavior before moving production traffic.

Compatibility guidance

Bringing an existing database?

Use Migrate to review schemas and mappings, copy records and verify the result before switching your application.

Explore Migrate

Build with OriginChainDB

Make OriginChainDB part of your stack.