Publish SDKs and MCP Servers

Prerequisites

• The Speakeasy CLI
• Speakeasy generated SDKs or MCP servers
• Access tokens or credentials for target package managers

Supported package managers

Naming packages

Publishing packages

1. Start publishing configuration

speakeasy configure publishing

Select the existing SDK targets to configure publishing. If no SDK targets are available, run speakeasy configure targets first.

2. Verify configuration files

Once configuration is complete, the following files will be generated or updated:

• .speakeasy/workflow.yaml – Speakeasy workflow configuration.
• .github/workflows/sdk_generation.yaml – GitHub Action to generate SDKs.
• .github/workflows/sdk_publish.yaml – GitHub Action to publish SDKs.

3. Set up repository secrets

1. Navigate to GitHub repository Settings > Secrets & Variables > Actions.
2. Click New repository secret.
3. Add SPEAKEASY_API_KEY (if needed) and any other required tokens (e.g., NPM_TOKEN).

5. Push changes and verify

Commit and push the updated workflow files. Once GitHub receives the generated SDK, manually kick off publishing for the first version.

6. Complete language-specific configuration

Java and C# require additional setup after running speakeasy configure publishing.

Java Maven: Sonatype Central Portal (recommended)

1. Create a Sonatype Central Portal account  (if needed).
2. Generate a Sonatype username and password for authentication . Save these for step 5.
3. Create a Sonatype namespace .
4. Create a GPG key to sign the artifacts . Save these for step 5.
   • Install GnuPG: brew install gnupg
   • Generate a key: gpg --gen-key. Note the key ID (e.g., CA925CD6C9E8D064FF05B4728190C4130ABA0F98) and short ID (e.g., 0ABA0F98).
   • Send the key: gpg --keyserver keys.openpgp.org --send-keys <keyId>
   • Note: The following key servers can also be used: keyserver.ubuntu.com, keys.openpgp.org, or pgp.mit.edu
   • Export the secret key: gpg --export-secret-keys --armor <shortId> > secret_key.asc
   • The file secret_key.asc will contain the GPG secret key.
5. Store the following secrets Github actions secrets:
   • OSSRH_USERNAME (the Sonatype username generated in Step 2)
   • OSSRH_PASSWORD (the corresponding password/token generated in Step 2)
   • JAVA_GPG_SECRET_KEY (the exported GPG key)
   • JAVA_GPG_PASSPHRASE (the passphrase for your GPG key)
6. In the java section of gen.yaml, provide the additional configuration required for publishing to Maven:

    java:
        #ensure the `groupID` matches the OSSRH org
        groupID: com.example
        #ensure the `artificatID` matches the artifact name:
        artifactID: example-sdk
        githubURL: github.com/org/repo
        companyName: My Company
        companyURL: https://www.mycompany.com
        companyEmail: info@mycompany.com

C# NuGet

1. Create a NuGet  account.
2. Create a NuGet API key:
   • Set the Package Owner field to the user or organization that will “own” the SDK artifact.
   • Ensure the API key has the relevant Push scope. If the package already exists, the API key may not need “Push new packages and package versions” permissions.
   • Populate the Glob Pattern and Available Packages fields in a way that allows publishing the SDK. Use the packageName specified in the gen.yaml file.
3. Store the NUGET_API_KEY in the GitHub Actions secrets.
4. In the C# section of gen.yaml add:

       csharp:
           packageName: MyPackageName # Ensure this matches the desired NuGet package ID
           packageTags: sdk api client # Provide space-separated tags for searching on NuGet
           enableSourceLink: true # Enables publishing with Source Link for better debugging
           includeDebugSymbols: true # Includes .pdb files for publishing a symbol package (.snupkg)

5. In the info section of the OpenAPI document, describe what the package is for in the description property. It will be set as the Package description , visible when searching for the package on NuGet.

   openapi: 3.1.0
   info:
     description: This description will be visible when searching for the package on NuGet.

6. In the externalDocs section of the OpenAPI document, provide the website’s homepage in the url property. It will be set as the Project URL , visible in the package’s “About” section.

   openapi: 3.1.0
   externalDocs:
       url: https://homepage.com/docs
       description: Public Docs

7. In the root of the repository:
   • Add a LICENSE[.md|.txt] file (see Licensing  for more details).
   • Add a 128x128 dimension image file called icon[.jpg|.png]to display on the NuGet package page.
   • Review the NUGET.md file, which is similar to the main README.md but excludes the SDK Installation and Available Operations sections. For more details, see Editing SDK Docs.

PHP

1. Create a Packagist  account and manually create the Packagist package.
2. Generate a Main API Token:
   • Navigate to Packagist Profile  and log in.
   • Record the “Main API Token” under account settings.
3. Update GitHub Action Secrets with Packagist credentials:
   • Navigate to the repository’s Github Secret Settings.
   • Update the following secrets:
     • PACKAGIST_TOKEN: Set this to the Main API Token from step 2.
     • PACKAGIST_USERNAME: Set this to Packagist username.
4. Store the following secrets in the GitHub Actions secrets:
   • PACKAGIST_TOKEN
   • PACKAGIST_USERNAME
5. Confirm that the publishing job is properly set up with the updated credentials. Note: Package name is read from composer.json name field.

TypeScript: Publishing private packages to npm

For TypeScript SDKs, publish private packages to npm by configuring both the package name and publish settings in the gen.yaml file.

Requirements for private npm packages:

• Package name must be scoped (e.g., @organization/package-name)
• npm access token with appropriate permissions
• publishConfig.access: restricted in package.json

Configuration steps:

1. Set a scoped package name in the gen.yaml:

typescript:
  packageName: '@example/openapi'

2. Add the private publishing configuration:

typescript:
  packageName: '@example/openapi'
  additionalPackageJSON:
    publishConfig:
      access: restricted

This configuration generates a package.json that looks like:

{
  "name": "@example/openapi",
  "version": "0.0.3",
  "author": "Speakeasy",
  "publishConfig": {
    "access": "restricted"
  }
}

3. Ensure the NPM_TOKEN (configured in step 3) has the necessary permissions to publish to the organization’s private packages.

TypeScript: npm granular access tokens

The npm registry requires granular access tokens for publishing packages. Classic tokens are deprecated; use granular tokens instead.

Generating a granular access token:

1. Log in to your npm account 

2. Navigate to Access Tokens in your account settings

3. Click Generate New Token and select Granular Access Token

4. Configure the token with the following settings:

   • Token name: Choose a descriptive name (e.g., speakeasy-sdk-publishing)
   • Expiration: Default is 7 days, but can be extended up to 1 year for automation workflows
   • Packages and scopes: Select Read and write permission for the packages you want to publish
   • For organization packages, ensure you have the appropriate organization permissions

5. Copy the generated token and store it securely as the NPM_TOKEN secret in your GitHub repository

Migrating from a monorepo to a dedicated repository

When moving a Speakeasy-generated SDK from within a monorepo to its own dedicated repository, follow these steps to ensure a smooth transition.

Setting up the new repository

1. Create a new repository (can be public or private)
2. Copy the SDK configuration files to the root of the new repository:
   • .speakeasy/gen.yaml
   • .speakeasy/workflow.yaml
   • overlay.yaml (if using)
3. Update package configuration files to reflect the new repository location:
   • For TypeScript: Update package.json
   • For Python: Update setup.py or pyproject.toml
   • For Go: Update go.mod
   • For other languages: Update the respective package metadata files

GitHub Actions configuration

Copy the GitHub Actions workflows to the new repository under .github/workflows/. Important considerations:

• Remove any working_directory settings that referenced the old monorepo structure
• Ensure the following secrets are configured in the new repository:
  • GITHUB_TOKEN
  • Package manager tokens (e.g., NPM_TOKEN, PYPI_TOKEN)
  • SPEAKEASY_API_KEY

Benefits of a dedicated repository

• Cleaner build process without workspace dependencies
• Easier configuration of linting and other tools
• Simplified version control and release management
• Direct GitHub issues integration for better user support
• Independent versioning and release cycles

Publishing in the Speakeasy dashboard

The SDK publishing tab in the Speakeasy dashboard provides an overview of the publishing history and offers various utilities for setting up and maintaining SDK publishing.

app.speakeasy.com

If package manager secrets were not set during the initial SDK repo setup, the publishing dashboard provides an interface to attach these secrets to the repository.

app.speakeasy.com

For GitHub actions set up with mode:pr, the publishing dashboard highlights open PRs in the SDK repo that are pending release. This view displays the exact SDK version that will be published upon merging the PR.

app.speakeasy.com