Integrations

Fits the stack you already run.

Gravity reads your code, lives in your pipeline, signs in through your identity provider and feeds your AI tooling — so it slots into how your team already works, not the other way round.

No marketplace of logos you’ll never use. See the enterprise controls.

One hub, your stack
GravityYour docs
Source & CI
Identity
AI & agents
Import

Source, identity, AI tooling and your old docs — all wired to one source of truth.

The ecosystem

One hub, wired to your stack

Everything you already use plugs into one source of truth — your code, your CI, your identity provider, your AI tooling and your old docs.

GravityYour docs
Source & CI
Identity
AI & agents
Import
GoOpenAPIAPI gatewaysGitHub ActionsGitLab CICircleCISAMLOIDCOktaMicrosoft EntraMCPClaudeCursorGitBookMarkdownGit
GoOpenAPIAPI gatewaysGitHub ActionsGitLab CICircleCISAMLOIDCOktaMicrosoft EntraMCPClaudeCursorGitBookMarkdownGit
GoOpenAPIAPI gatewaysGitHub ActionsGitLab CICircleCISAMLOIDCOktaMicrosoft EntraMCPClaudeCursorGitBookMarkdownGit
GoOpenAPIAPI gatewaysGitHub ActionsGitLab CICircleCISAMLOIDCOktaMicrosoft EntraMCPClaudeCursorGitBookMarkdownGit
The trigger

A push lands

Your CI build calls Gravity, just like any other check.

Where it plugs in

Connected at every step

Four places Gravity meets your stack — each shown working, not just claimed.

Source & CI

Lives in the pipeline you already run

Gravity reads your code and runs as a step in your build, so doc changes are proposed where the work already happens — not in a separate tool nobody opens.

  • Go and OpenAPI analysis, tied back to source
  • GitHub Actions, GitLab CI and CircleCI
  • Drift caught on every build, before it ships
ci · docs

Identity & SSO

Signs in through your identity provider

Your security team keeps control. People sign in through the provider you already run, and their access maps from the directory groups they are already in.

  • SAML and OIDC single sign-on
  • Okta, Microsoft Entra and other IdPs
  • Roles mapped from your directory groups
SAML / OIDCvia your IdP
Gravity
Identity provider
Directory groupeng-platform
Mapped roleEditor

AI & agents

Feeds the AI tooling your team uses

Your published docs become memory your assistants can read over MCP — so Claude, Cursor and other clients answer from your real content, with citations.

  • Read and write surfaces over MCP
  • Works with Claude, Cursor and MCP clients
  • Cited answers drawn from your own docs
MCPYour docs

Import & migrate

Brings your existing docs across

Move what you already have without a rewrite. Gravity imports your spaces and Markdown, keeps the structure and links intact, and lands it as a draft to review.

  • GitBook spaces with their hierarchy
  • Markdown straight from your repo
  • Links, redirects and structure preserved
9 GitBook spaces mapped

At a glance

Works with your tools

The ecosystems Gravity plugs into today — hover to pause the strip.

GoOpenAPIAPI gatewaysGitHub ActionsGitLab CICircleCISAMLOIDCOktaMicrosoft EntraMCPClaudeCursorGitBookMarkdownGit
GoOpenAPIAPI gatewaysGitHub ActionsGitLab CICircleCISAMLOIDCOktaMicrosoft EntraMCPClaudeCursorGitBookMarkdownGit
GoOpenAPIAPI gatewaysGitHub ActionsGitLab CICircleCISAMLOIDCOktaMicrosoft EntraMCPClaudeCursorGitBookMarkdownGit
GoOpenAPIAPI gatewaysGitHub ActionsGitLab CICircleCISAMLOIDCOktaMicrosoft EntraMCPClaudeCursorGitBookMarkdownGit

Source & CI

Gravity reads your code and lives inside your pipeline, so docs are proposed where you already work.

  • Go & OpenAPI analysis
  • GitHub Actions, GitLab CI, CircleCI
  • Drift checks on every build

Identity & SSO

Sign in through the identity provider your security team already runs.

  • SAML & OIDC single sign-on
  • Okta, Microsoft Entra & more
  • Roles mapped from your directory

AI & agents

Your published docs become memory your AI tooling can read over MCP.

  • MCP read & write surfaces
  • Claude, Cursor & MCP clients
  • Cited answers from your content

Import & migrate

Bring your existing content across without a rewrite.

  • GitBook spaces & hierarchy
  • Markdown from your repo
  • Links & structure preserved

Getting wired in

Three small steps, not a project

No platform migration, no rip-and-replace. Most teams have Gravity in their pipeline inside an afternoon.

01

Point it at a repo

Connect a repository and Gravity reads the code and your API surface to draft the first reference.

02

Add it to CI

Drop one step into your existing pipeline so every build checks for drift and proposes updates.

03

Connect your IdP

Wire up SAML or OIDC so your team signs in through the provider you already run.

Bring Gravity into your workflow.

Point it at your repo, wire it into CI, and connect your identity provider — usually in an afternoon.