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

# Para Server SDK

> An introduction to server-side integrations with Para

Para's Server SDK enables you to perform blockchain operations on the server-side across Node.js, Bun, Deno, and Cloudflare Workers environments. The server SDK shares the same core functionality as the web SDK, with authentication being the primary difference.

<Tip>
  The Server SDK only works with Embedded Wallets. For connecting to and signing with external wallets such as MetaMask and Phantom, you
  will need to integrate one of Para's Client SDKs.
</Tip>

<Note>
  **Non-Node.js runtimes** (Bun, Deno, Cloudflare Workers) require `disableWebSockets: true` in the constructor.
  See the [setup guide](/v3/server/setup#runtime-compatibility) for details.
</Note>

## Getting Started

<Card title="Server Setup" imgUrl="/images/v3/general-server.png" href="/v3/server/setup" description="Learn how to install and configure the Para Server SDK in your backend environment." horizontal />

## Blockchain Ecosystem Support

Para works seamlessly with major blockchain ecosystems on the server-side, allowing you to leverage Para's authentication alongside chain-specific libraries:

<CardGroup cols={3}>
  <Card title="EVM Integration" imgUrl="/images/v3/network-evm.png" href="/v3/server/guides/evm" description="Use Para with Ethers and other EVM-compatible libraries on the server." />

  <Card title="Solana Integration" imgUrl="/images/v3/network-solana.png" href="/v3/server/guides/solana" description="Integrate Para with Solana libraries in server environments." />

  <Card title="Cosmos Integration" imgUrl="/images/v3/network-cosmos.png" href="/v3/server/guides/cosmos" description="Use Para with CosmJs on the server." />

  <Card title="Stellar Integration" imgUrl="/images/v3/network-stellar.png" href="/v3/server/guides/stellar" description="Use Para with the Stellar SDK on the server." />
</CardGroup>

## Authentication Options

<Note>
  Creating new wallets from your server? The [REST API](/v3/rest/overview) is the recommended path — Para holds the key
  material, so there is no user share to manage. Use the Server SDK when importing client sessions or when an existing
  integration relies on SDK pregen.
</Note>

Para offers two authentication methods for server-side applications:

<CardGroup cols={2}>
  <Card horizontal title="Server Sessions" imgUrl="/images/v3/general-sessions.png" href="/v3/server/guides/sessions" description="Import client-side authenticated sessions to perform operations on behalf of users." />

  <Card horizontal title="Pregenerated Wallets" imgUrl="/images/v3/feature-pregeneration.png" href="/v3/server/guides/pregen" description="SDK-based pregeneration for flows that need direct user-share control." />
</CardGroup>

## Resources

<CardGroup cols={2}>
  <Card title="Examples" imgUrl="/images/v3/framework-node.png" href="/v3/server/examples" description="Explore real-world examples of Para Server SDK implementations." horizontal />

  <Card title="Troubleshooting" imgUrl="/images/v3/general-help.png" href="/v3/general/troubleshooting" description="Solutions for common issues when working with Para Server SDK." horizontal />
</CardGroup>