> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rkat.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Port and reuse an integration

> Reuse provider logic and portable metadata while keeping framework runtimes and authority local to their owners.

Start by identifying what the donor actually contributes: a maintained provider client, an MCP server, a tool wrapper, a setup skill, or a complete application runtime. The useful reusable unit is often smaller than the donor framework.

<Steps>
  <Step title="Record exact provenance">
    Retain source URL, revision or artifact digest, license, dependency notices and the behavior being reused. Distinguish copied implementation, a dependency and a documentation-based reimplementation. Check distribution rights before packaging private donor code.
  </Step>

  <Step title="Separate operations from framework machinery">
    Extract explicit provider requests, bounded parsing and receipt handling. Replace donor-specific agent decorators, session creation, credential globals and approval bypasses with narrow host inputs. Meerkat remains the runtime; Meta remains application composition.
  </Step>

  <Step title="Map authority and lifecycle">
    Identify the selected account, resource policy, credential owner, event/delivery semantics, state migration and shutdown behavior. If the donor assumes one global user, define and test the account boundary before advertising multi-account support.
  </Step>

  <Step title="Select an acquisition form">
    Use an independent remote/local MCP component, typed adapter, CLI pack or frontend package as appropriate. A CLI strategy still needs executable identity, environment, output limits, process lifecycle and actual operation policy.
  </Step>

  <Step title="Validate equivalence and missing behavior">
    Cover pagination, limits, redirects, cancellation, replay, failures and license artifacts. Carry forward required business semantics while documenting unsupported donor features. Installed-artifact and live-account evidence remain separate checks.
  </Step>
</Steps>

## Reuse in an application

Keep application policy, grants, recipient selection and domain formatting in the host. Share the provider operations, transport cleanup and durable output components across applications.

## Portable metadata

Connect parses Agent Plugins and MCPB metadata into inert descriptions. Import success does not prove executable compatibility, sandboxing, credential correctness or full donor-platform compatibility. A component that requires Connect host services cannot be exported as a generic MCP entry that silently discards them.

Read [portability](/connect/reference/portability) and [distribution](/connect/availability#distribution) before choosing a delivery format.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.