GitHub interactive images MCP app ​

Sign in to your Workato account and go to the project where you plan to add your GitHub connection.

Click Create > Connection (or press C twice), then select GitHub as your connection.

Provide a Connection name that identifies which GitHub instance Workato is connected to.

Use the Location drop-down menu to select the project where you plan to store the connection.

Use the Authentication type drop-down menu and select OAuth App.

Optional. Click Advanced configuration to display the Host name field.

Optional. Enter a Host name. This is applicable when using Github Enterprise Server. Enter your Github subdomain. For example, if your host URL is https://github.example-organisation.com, the subdomain is github.example-organisation.com.

Click Connect. Workato redirects you to GitHub. The OAuth App requests authorization to act on your behalf. Workato performs actions such as creating comments, issues, and pull requests under your GitHub user.

Complete the steps in the GitHub documentation to register your GitHub App.

Retrieve your GitHub App ID in the General settings page of your GitHub app.

Save this App ID and place it into your connection

Generate a Private key on the same page. GitHub automatically downloads this .pem file to your machine.

Generate the private key

Open the .pem file in a text editor. The file should look similar to the following:

-----BEGIN RSA PRIVATE KEY-----
MIIEpAIBAAKCAQEAyL/wuiSaWoH0pyf366G5E7dbzzmON1qMMrWvls8RtZtgOLjb
FBxj6gO2aUfoGbMCMqOYRV6xCn6tK118sGYMd5U/kCFu3IRPr/2GoEtcrf0TecQG
ON+27ijH0Vpn62o8NzGejdy0AWujrtAl6F8xGZeze0PzrGvW6h/GnAdZO1gJnp8t
wmEqEMXqAsPOQ0hkY+r+pE8RKQVsJCe+PIanBKp7RKWDi9usPFZQdQ==
-----END RSA PRIVATE KEY-----

Copy the entire private key, including the -----BEGIN RSA PRIVATE KEY----- and -----END RSA PRIVATE KEY-----. Use this private key when you set up the connection in Workato.

Retrieve your Installation ID from the organization or user where you installed your GitHub App:

• Users accounts: Go to Settings > Applications > Your GitHub App > Configure.
• Organizations: Go to your organization's GitHub homepage. Click Settings > Installed GitHub Apps > Configure.

The installation ID appears in the URL. For example, if the URL is https://github.com/settings/installations/13876669, the installation ID is 13876669.

Save the installation ID. Enter this ID when creating the GitHub App connection in Workato.

Provide a Connection name that identifies which GitHub instance Workato is connected to.

Use the Location drop-down menu to select the project where you plan to store the connection.

Use the Authentication type drop-down menu and select GitHub App.

Enter your GitHub App ID.

Enter your Github App Private key.

Enter your Installation ID.

Optional. Click Advanced configuration to display the Host name field.

Optional. Enter a Host name if using GitHub Enterprise Server. Use your GitHub subdomain. For example, if your host URL is https://github.example-organisation.com, the subdomain is github.example-organisation.com.

Optional. Enter a Custom OAuth profile. This selection ensures that all requests to the app use the specified profile.

Click Connect.

Go to Github account > Settings > Developer settings > Personal access tokens > Generate new token.

Click Generate new token.

Copy the token. Enter this token in Workato to authenticate the connection.

Sign in to your Workato account and go to the project where you plan to add your GitHub connection.

Click Create > Connection (or press C twice), then select GitHub as your connection.

Provide a Connection name that identifies which GitHub instance Workato is connected to.

Use the Location drop-down menu to select the project where you plan to store the connection.

Use the Authentication type drop-down menu and select Personal Access Token.

Optional. Click Advanced configuration to display the Host name field.

Optional. Enter a Host name. This is applicable when using Github Enterprise Server. Enter your Github subdomain. For example, if your host URL is https://github.example-organisation.com, your subdomain is github.example-organisation.com.

Enter your Personal Access Token.

Optional. Enter a Custom OAuth profile. This ensures all requests to the app use the specified profile.

Click Connect.

Go to Projects and click Create > Skill.

Enter a name for the skill in the Skill name field.

Use the Location drop-down menu to select the project where you plan to store the skill.

Click Start building.

The recipe editor opens with the Start workflow trigger and Return response action automatically selected.

Enter the following description for your skill workflow in the When should this skill run? field. This description helps the LLM recognize when to fetch a file from a GitHub repository versus when a user asks a general question.

Fetch a file (such as PNG, JPG, SVG, or other binary/text file) from a GitHub repository. Returns the file contents (base64-encoded for binary files) along with metadata like size, encoding, and download URL.

Enter a description for the skill

Go to the What inputs does this skill need to run? section and click Use JSON.

Copy and paste the following JSON schema to provide a description of the schema recipe parameters:

[
  {
    "name": "owner",
    "type": "string",
    "optional": false,
    "control_type": "text",
    "hint": "Repository owner (user or organization), such as 'octocat'"
  },
  {
    "name": "repo",
    "type": "string",
    "optional": false,
    "control_type": "text",
    "hint": "Repository name, such as 'Hello-World'"
  },
  {
    "name": "path",
    "type": "string",
    "optional": false,
    "control_type": "text",
    "hint": "File path within the repository, such as 'images/logo.png'"
  },
  {
    "name": "ref",
    "type": "string",
    "optional": true,
    "control_type": "text",
    "hint": "Optional branch name, tag, or commit SHA. Defaults to the repository's default branch."
  }
]

Go to the What information does this skill send back? section and click Use JSON.

Copy and paste the following JSON schema to define the skill output:

[
  {
    "name": "name",
    "type": "string",
    "optional": true,
    "control_type": "text"
  },
  {
    "name": "path",
    "type": "string",
    "optional": true,
    "control_type": "text"
  },
  {
    "name": "sha",
    "type": "string",
    "optional": true,
    "control_type": "text"
  },
  {
    "name": "size",
    "type": "integer",
    "optional": true,
    "control_type": "number"
  },
  {
    "name": "type",
    "type": "string",
    "optional": true,
    "control_type": "text"
  },
  {
    "name": "encoding",
    "type": "string",
    "optional": true,
    "control_type": "text"
  },
  {
    "name": "content",
    "type": "string",
    "optional": true,
    "control_type": "text",
    "hint": "File contents. Base64-encoded for binary files (PNG/JPG/SVG/etc.)."
  },
  {
    "name": "download_url",
    "type": "string",
    "optional": true,
    "control_type": "text"
  },
  {
    "name": "html_url",
    "type": "string",
    "optional": true,
    "control_type": "text"
  },
  {
    "name": "git_url",
    "type": "string",
    "optional": true,
    "control_type": "text"
  },
  {
    "name": "url",
    "type": "string",
    "optional": true,
    "control_type": "text"
  },
  {
    "name": "error",
    "type": "string",
    "optional": true,
    "control_type": "text"
  }
]

Click Save.

Click + Add step and select Action in app.

Click Add step > Action in app

Search for GitHub and select it as your app.

Select Custom action.

Enter a name in the Action name field. For example: Get repository image contents.

Set up the action

Use the Method drop-down menu to select GET.

Go to the Path field and switch to formula mode.

Copy and paste the following formula into the Path field, replacing each datapill placeholder, such as <RefStep 1 datapill>, <OwnerStep 1 datapill>, <RepoStep 1 datapill>, and <PathStep 1 datapill>, by mapping the corresponding datapill from the RECIPE DATA panel:

<RefStep 1 datapill>.present? ? '/repos/' + <OwnerStep 1 datapill> + '/' + <RepoStep 1 datapill> + '/contents/' + <PathStep 1 datapill> + '?ref=' + <RefStep 1 datapill> : '/repos/' + <OwnerStep 1 datapill> + '/' + <RepoStep 1 datapill> + '/contents/' + <PathStep 1 datapill>

The resulting formula should look like this:

Path formula

Ensure that Response type is set to JSON response.

Expand the Request headers section and click Add header.

Enter Accept in the Name field and application/vnd.github+json in the Value field.

Go to the Response body section and click Use JSON.

Copy and paste the following schema into the field:

[
  {
    "control_type": "text",
    "name": "name",
    "type": "string"
  },
  {
    "control_type": "text",
    "name": "path",
    "type": "string"
  },
  {
    "control_type": "text",
    "name": "sha",
    "type": "string"
  },
  {
    "control_type": "integer",
    "name": "size",
    "type": "integer"
  },
  {
    "control_type": "text",
    "name": "type",
    "type": "string"
  },
  {
    "control_type": "text",
    "name": "encoding",
    "type": "string"
  },
  {
    "control_type": "text",
    "name": "content",
    "type": "string"
  },
  {
    "control_type": "text",
    "name": "download_url",
    "type": "string"
  },
  {
    "control_type": "text",
    "name": "html_url",
    "type": "string"
  },
  {
    "control_type": "text",
    "name": "git_url",
    "type": "string"
  },
  {
    "control_type": "text",
    "name": "url",
    "type": "string"
  }
]

Click Save.

Click the RETURN response step in the recipe editor.

Map the NameStep 2 datapill to the Name field.

Map the corresponding datapills for the RETURN response

Map the PathStep 2 datapill to the Path field.

Map the ShaStep 2 datapill to the Sha field.

Map the SizeStep 2 datapill to the Size field.

Map the TypeStep 2 datapill to the Type field.

Map the EncodingStep 2 datapill to the Encoding field.

Map the ContentStep 2 datapill to the Content field.

Map the Download URLStep 2 datapill to the Download URL field.

Map the Html URLStep 2 datapill to the Html URL field.

Map the Git URLStep 2 datapill to the Git URL field.

Map the URLStep 2 datapill to the URL field.

Click Save.